Such a feature is likely to be one of the top annoyances of people who have tried, but then given up, using Eastwood, for lack of such a feature.
@andy.fingerhut what thoughts are those ๐ edit: I filed an issue if you'd like to chime in there (incase slack messages disappear): https://github.com/jonase/eastwood/issues/282
I can add a comment on that issue.
@noisesmith an issue would be appreciated, and a PR even more so ๐
Iโve done a simple work around for the deprecated
linter, in which the config takes a set of regular expressions to match on vars you donโt care about being deprecated.
This approach โworksโ for any linter that works on vars, but does not offer the granularity of expressions/forms
Also, a downside to this approach is that itโs done in the config and not in the code
For vars I guess one could imagine using meta-data (which obviously has been discussed before), but we might also have to acknowledge that different linters need different approaches to disable warnings.
I added some comments to that issue linked above. Feel free to ask questions in comments there, or here. There is more than one way to do it, of course -- the note there is just what I was considering implementing.
Thanks, I think that context helps ๐ might try to take a stab... sometime