WebParser classification change (cosmetic)
Aethrios opened this issue · comments
Just a heads up, 4.1 pushed WebParser to be considered both a plugin (this will be supported forever, evidently) and a measure. As I'm trying to roll my skins over to follow the new classification, I'd love to not have to see all my instances of WebParser highlighted in red like they're wrong.
This is entirely a cosmetic change I'm looking for here. Hope this helps you stay in the loop!
Sauce: https://docs.rainmeter.net/manual/measures/webparser/#ParentChild
https://forum.rainmeter.net/viewtopic.php?f=13&t=27744
Thanks for the heads-up. I am not sure how I missed that oO
- Add plugins as measures
- Added measures to smart completion
- Removed Plugins from Smart Completion
- Bumb to version 2.19.0
- Mark plugins as deprecated as stated
- Added release notes
- Publish on Rainmeter Forums
However, new skins created going forward should use the correct syntax for accuracy and clarity.
Added syntax highlighting for the measures
The new measures are supported in the smart completion
Removed the plugins from smart completion but since it still is supported we require backward compatibility.
Deprecated the old plugin statements