4 ms·
This is awesome! I'd love if you could do things like help upgrade library versions that have breaking changes--say something like generate a PR to go from Reac
by davebryand 8y ago
This is awesome! I'd love if you could do things like help upgrade library versions that have breaking changes--say something like generate a PR to go from React 16 to React 17, for instance.
It would also be cool if this could help generate code in the best-practice style defined by third-party libraries. For instance, if the Redux team defined the canonical way to define a selector, it would be handy to be able to have Optic use that information to generate selectors for me. This would take something like create-react-app and break down the best practices into more bite sized chunks.
Really excited about this!
- addcn 8y agoGreat ideas. We’ve experimented with doing version migrations before and I think it’s definately something we will have good support for in the next several months. If you haven’t read about our Optic Markdown it’s designed for what you’re describing. A team could specify their conventions and best practices in Markdown and Optic will use the example code in the generators.