I’m sharing a few bugs I’ve found recently and I’ll be adding to the reply itself if I find any in the future, we should probably have an issue tracker for this kind of thing, look into @ussaaron’s v0toolkit suggestions.
Version card no longer provides link to the file to directly open in code-editor
Build speed has reduced, probably has to do with the project size but I often have to reload to get the preview working.
Toggle on and off the diff tool, then try to use the code editor, when trying to move the cursor using arrows it takes more steps than intended, when using backspace it clears more characters, when trying to use the replace shortcut (Ctrl+D) it replaces more words.
Toggle on the diff tool in one file and try to change a file where there is no diff, older file that wasn’t changed recently, it won’t allow you to but if you go to any file that was changed recently and toggle the diff tool off, it will work normally again.
My older chats do still allow, but I think it’s how the agent presents the response that’s causing this difference. Agent only responds with what files were changed without attaching the links to them probably.
In chats where there were version cards with the working links, newer prompt also seem to have the same response presentation. Do you want me to provide the diff tool issue example that you have quoted?
Earlier, when we hovered over “layout” or “page” as listed in the card attached, they used to get highlighted as links. If we clicked on that link, it used to take us to that file in the code editor directly, now we need to search for these files in the file tree next to the code editor.
Guys, I figured out why this is happening and I think I fixed it. Basically what is happening is that the action card generated by your scripts is locking your file click focus access. So if you look at your thread you will see an action card for your scripts. I bet you can still click on that right? And that will open the script for that action right? Ok so if you delete that script after completing the action then it should give you your standard file click action back. The issue of course is that v0 will often create scripts to run in error, so they may just go unused and permanently trap focus for file click. This solution worked for me. but go ahead and try it yourself. Oh also you need to get v0 to make a change after deleting the scripts in order to see focus and clickability return to regular changed files. I’m certain with > 99% confidence that this is the root issue and solution. Obviously the best solution would be to make it so focus on file click isn’t trapped by the actions card since the action card is > 50% redundant or wrong.
