Skip to content
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

Idea: Instead of scanning for deprecation messages, pre-specifiy regexes for all known deprecations #22

Open
mrandre opened this issue Aug 14, 2015 · 0 comments

Comments

@mrandre
Copy link

mrandre commented Aug 14, 2015

I noticed when I did my initial run-through that there were many duplications of the sort "you tried to access property 'x' but you should have used 'model.x'"

So I went through and collapsed them into regexes, problem solved. It occurred to me there are a finite number of possible deprecations, so maybe it would be easier to just put all those regexes in a file and copy that into config instead. No console copy-paste, covers everything by default, less likely to have new things crop up later.

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

No branches or pull requests

1 participant