✅ Deploy Preview for keda ready!

Name	Link
🔨 Latest commit	33d27ce
🔍 Latest deploy log	https://app.netlify.com/projects/keda/deploys/683e77f0e0503100086b0225
😎 Deploy Preview	https://deploy-preview-1574--keda.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Thank you for your contribution! 🙏 We will review your PR as soon as possible.

While you are waiting, make sure to:

• Add your contribution to all applicable KEDA versions
• GitHub checks are passing
• Is the DCO check failing? Here is how you can fix DCO issues

Learn more about:

• How to become a listed end-user or a listed commerical offering
• Our contribution guide

The question here is, do we change the documentation, or do we change the name of the scaler? All scalers end with '_scaler'. So I personally advocate harmonizing this and therefore changing the file name in keda.

Of course, I don't decide this alone, so I'm curious to hear the opinion of a maintainer or an other KEDA Reviewer.

The question here is, do we change the documentation, or do we change the name of the scaler? All scalers end with '_scaler'. So I personally advocate harmonizing this and therefore changing the file name in keda.

That's a really interesting point, I'd rename the scaler file too to align with other scalers

Hi @aniruddhc1!

Thanks for this PR! Great find! Is it possible for you to rename the files in keda?

This concerns both, temporal.go and temporal_test.go

#1573 and #1574 may then be closed

Happy to!