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

Improve When not to codemod guide #138

Open
danieldelcore opened this issue Jul 4, 2022 · 0 comments
Open

Improve When not to codemod guide #138

danieldelcore opened this issue Jul 4, 2022 · 0 comments
Labels
📚 docs Improvements or additions to documentation

Comments

@danieldelcore
Copy link
Contributor

danieldelcore commented Jul 4, 2022

https://www.codeshiftcommunity.com/docs/when-not-to-codemod

This guide should also recommend, other migration strategies:

It’s quite hard to follow references across module boundaries, it is possible if you consider requiring, parsing and mutating that file in your codemod, but it’s not something i’ve done personally so not entirely sure it will work for you.

- Create a facade prop that will make your API backward compatible for a limited time.
- Create a eslint rule to warn/guard against its current/future use
- Write product code in a more static analysable way
- Prompt for human input

Also consider changing the name to something more friendly

@danieldelcore danieldelcore added the 📚 docs Improvements or additions to documentation label Jul 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📚 docs Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant