Open with-heart opened 2 months ago
I can see where you're coming from with this one, copying the generated/updated codemod to the codemod panel should happen automatically in case it succeeds. Putting this in our Backlog.
That sounds great! I can't think of a time where it generated an update that I didn't want to try right away.
One thought that popped in my head with that solution is related to a question I just saw in Slack:
Since there's no "history" for the codemod code as it's being generated and updated, copying the code automatically would be a destructive action. I'm imagining a situation where an update causes codemod functionality that worked previously to stop working, and I'd have no way to get back to it or figure out what changed to break it.
cc @mohebifar
Issue Description
Select one of: [ ] Generated codemod is not correct [ ] Bug in Codemod Studio [x] UI/UX improvement request [ ] Feature request
It's easy to forget to click "Copy to Codemod panel" button when having a conversation that generates updated versions of a Codemod.
Steps to Reproduce
Or if you're me, the reason you're opening this issue is because your steps are 1-4 and then
Actual Results
Expected Results
The application helps make sure that the updated version's code is copied to the Codemod panel if that's what I failed but otherwise intended to do.
Intentionally left this vague because I think there are a lot of ways the app could do that.