Tell v0 this or it will go and break so many things that you will have to go back and spend time and money fixing!
DO NOT DO ANYTHING OTHER THAN THE CHANGES I REQUEST HERE
DO NOT DO ANY MOCK FUNCTIONALITY! (up to you if you want mock functionality obviously)
ONLY CHANGE THIS SCREEN:
SCREEN: Enter Screen Name !!!
CHANGE: THIS IS VERY SIMPLE (Tell it this or it will go and do some convoluted / complex rubbish that you will have to undo later)
Change Request Details!!!
1: CONFIRM NO OTHER SCREENS OR CODE WERE CHANGED
2: CONFIRM NO MOCKED DATA WAS CREATED OR EDITTED – THIS IS A PRODUCTION APPLICATION
3: CONFIRM YOU DID NOT BREAK ANYTHING
Just a suggestion… I have been undoing rubbish I did not ask for on other screens for a week.
It tries to be smart and do stuff you do not want! Up to you if you want it to do this.
Hope this helps!!
2 Likes
I locked files so it wouldn’t change them, And then it tried to change the locked files, but couldn’t and asked me to unlock the files so it can make changes when the files unlock.
then when I unlocked the file it implemented some queued up changes and broke the app instantly. noice
1 Like
Thanks for the feedback.
I also implemented STNs = Screen Tracking Numbers so that I can tell it exactly what screen to update.
I.e. Update STN:L1S1:R1 Level 1 Screen, Screen Number at that Level, Revision 1 so that it only changes that part of the code for that specific screen. Not a bad practice to keep now. I implemented a full screen map to track this like an Org Chart Tree with drop down buttons so I can track everything..
Slightly OCD but very easy to update and track.
1 Like
Great idea.
I just made a post about how I get it to make implementation plans and think about them a bit about how it might break stuff. It seems to reduce errors quite a bit.
1 Like