Share your product feedback!

Please tell us what we can do to make Lovable the best product for you.

Discard build errors

If there are build error warnings but there is nothing actually impacting… lovable offers to fix but… if you don’t accept, it tries to push that into the next prompt… I’ve had an instance where I had to roll back ‘build error’ fix from lovable where it changes how a component/page operates entirely which costs me credits.. then I get my design and functions back, lovable picks up build error and even though I ignore it… it keeps slipping into prompt ‘shall I fix this build error while I’m there’ it will keep doing this over and over and over until this build error is fixed so you are held to ransom with it. Should be able to click a button to ignore and be left alone until you decide you want to fix or if you want to

Rick Y 2 days ago

💡 Feature Request

Admin dashboard functionality creation crashes Auth completely

Hi team, I have now tried several times to create a solution where we can have different user tiers: non-paying, paying and admin, where each tier enables functionality beyond the initial ones (meaning a paying user has more features than a non-paying user and obviously an admin should be able to use all functionality and be able to view, edit and delete data of himself and other users, through a different route e.g., /admin that is not accessible for other either paying and non-paying users). I have tried to add this functionality to an existing app and it completely broke the system, essentially since then auth is in a complete loop and it can’t fix it (feels a bit like a ripoff when you spend all your messages to go through the loop again and again and again). Now I have tried again and just tried to create the basic auth functionality and user tier/admin functionality in a clean project and as soon as I introduce the RLS policy to allow admins to edit and view and delete data of other users again auth broke completely. Not sure anyone has a solution to this. Ultimately loveable is only relevant for me if I can turn the product in a webapp that users pay for and for this you obviously need admin capabilities that are not just actioned through supabase. Anyone found the same issue/has a solution for this? It’s extremely frustrating as everything else works so well incl. the edge functions but I’m now considering to drop the whole project.

Maximilian Czymoch 3 days ago

1
🐛

Bug Hunting