Skip to content

DEV: Improve template-override deprecations (stable) #32801

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: stable
Choose a base branch
from

Conversation

davidtaylorhq
Copy link
Member

These changes are backported from main, so that stable users receive better feedback about this upcoming deprecation.

  • Update Meta topic URLs

  • Add theme/plugin identification to deprecation

  • Enable admin warning banner

https://meta.discourse.org/t/355668

@davidtaylorhq davidtaylorhq force-pushed the stable-template-override-warnings branch from 9d6448b to 6d65e4a Compare May 19, 2025 16:53
These changes are backported from `main`, so that stable users receive better feedback about this upcoming deprecation.

- Update Meta topic URLs

- Add theme/plugin identification to deprecation

- Enable admin warning banner

https://meta.discourse.org/t/355668
@davidtaylorhq davidtaylorhq force-pushed the stable-template-override-warnings branch from 6d65e4a to 9fbd471 Compare May 19, 2025 16:53
@@ -31,11 +50,15 @@ export default {
}

let componentName = templateKey;
const finalOverrideModuleName = moduleNames[moduleNames.length - 1];
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🏌️

Suggested change
const finalOverrideModuleName = moduleNames[moduleNames.length - 1];
const finalOverrideModuleName = moduleNames.at(-1);

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good call! But will skip for now though, since I want to keep this backport as close to the main version as possible so that there are fewer conflicts on the next stable bump.

(and it's not worth changing in main, since we'll be dropping this initializer in a couple of weeks)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants