# Resolving the \`this-property-fallback\` deprecation **URL:** \ **Category:** Development\ **Tags:** dev-news\ **Created:** [November 21, 2024, 7:08pm UTC](https://meta.discourse.org/t/resolving-the-this-property-fallback-deprecation/337276 "2024-11-21T19:08:58Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\ **Post date:** [November 21, 2024, 9:29pm UTC](https://meta.discourse.org/t/resolving-the-this-property-fallback-deprecation/337276/2 "2024-11-21T21:29:53Z")
> [@david](#): > > if you use the latest version of our standard linting configuration (as per [the plugin skeleton](https://github.com/discourse/discourse-plugin-skeleton) and [the theme skeleton](https://github.com/discourse/discourse-theme-skeleton)), then all affected code will be automatically updated next time you run `ember-template-lint --fix`. That’s awesome! In one of my plugins where (I think I have) properly updated the lint config, I see a whole buch of instances of `{{this.blah}}` that I’m pretty darn sure weren’t there until recently. I can’t overstate how cool that is. 🎉 🥂 🍻 It would be nice if there were some automated way to copy/remove the proper files in each plugin when there was an update to the skeleton. (I may or may not have contrived to do that by hand this time.) Maybe it’d be possible to stick a little `bash` script into the skeleton that would check for `plugin.rb` in the current directory, and if it was there, it could copy stuff from where the script was into the current directory. Something like that. --- _[View the full topic](https://meta.discourse.org/t/resolving-the-this-property-fallback-deprecation/337276)._