So I’ve been trying to fix an issue by prompting for hours, maybe 60 prompts. And I just can’t figure it out. The thing is cmd + b triggers my sidebar, but v0 insists there is no trigger for cmd+b in any code governing my sidebar.
I double check, in components/ui/sidebar.tsx - v0 is right.
Then I download the codebase and A) there are a ton more files here. and B) sidebar.tsx looks completely different in the dowloaded code. and absolutely has a trigger for cmd + b…
This seems like a huge bug. luckily confirms I’m not mad. but frustrating to try and solve some hidden setting.
I’ve been having a ton of issues completing even simple tasks in v0 over the last few days / week, with v0 struggling to understand the issue and guiding me on long journeys to find workarounds that wasted a lot of time. and sometimes stalling mid file edit.
I feel this bug could be an explanation for a lot of this and not be isolated to this one project. Hope you’ll investigate
Looked a bit closer and it seems this is part of the imported Shadcn component. Why are you not letting the v0 user access and edit these, when they affect the apps we’re developing?
V0 is very restrictive on which folders it gives access to, and I guess there are product / ux reasons for it, but here’s an example how convoluted it can make the process, and how it can sabotage the development experience.
How about having some advanced mode that gives these accesses? Or what is your recommendation for me to fix my issue?
the problem is the CMD+B binding conflicts with my CMS text editor bindings. but I can’t change them, because they are part of the shadcn template which is not part of the filesystem v0 chooses to show me or let me or the agent edit.
