codemod-com
[studio] It's easy to forget to click "Copy to Codemod panel" button when having a conversation that generates updated versions of a Codemod
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
- Fill out Before and After
- Click "Autogenerate with Codemod AI"
- Notice that generated code is now in the Codemod panel
- Send a message to Codemod AI that causes it to generate an updated version of the existing Codemod
- Notice that the updated version's code isn't in the Codemod panel
- Find the "Copy to Codemod panel" button (typically by scrolling up)
- Click "Copy to Codemod panel" button
- Notice that the updated version's code is now in the Codemod panel
Or if you're me, the reason you're opening this issue is because your steps are 1-4 and then
- Fail to notice that the updated version's code isn't in the Codemod panel
- Get frustrated that the "updated" Codemod still isn't working
- Repeat 4-6 with increasing frustration until you notice that the updated version's code isn't in the Codemod panel
- Weep
Actual Results
- it's easy to forget that updated versions of the Codemod aren't automatically copied
- the "Copy to Codemod panel" button is typically not even in view once the AI is done responding
- the "Copy to Codemod panel" button has no visual indication that if I've just generated an updated version of the codemod, clicking it might be the thing I want to do next
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.
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.
