Trouble with Component Conversion to Elements

[ryancode (Ryan)]

I’m attempting to build a full web app as a no-code founder. I’ve been using ChatGPT to help me strategize and walk me through, and I’m starting to regret using it or potentially using WeWeb because it seems to have been trained on various previous version of WeWeb. I have a list of a dozen topics that it struggles to help me with, but this latest one seems completely wrong. I’m attempting to turn a component into its corresponding original elements because of another issue I’m having mapping data from supabase to this list (formerly repeatlist or collectionlist aka another issue I had) of components, and I came across this answer from google. Is this correct? Why in the world would WeWeb decide to stop the ability to convert a component into its elements? So the only options are to edit every single component, or to build the exact same from from scratch every time? Am I missing something?

[sam1 (sam)]

chatGPT will be outdated as weweb is constantly updating. use if for general strategy or for specific help on things like custom JS.

im not sure I fully understand your question. did you make a component out of weweb elements and now want it not to be a component? if so thats never been a thing. you can just copy the elements out of the component tho but obviously if you have bound things to the properties of your component it will be unbound ect.

To me it sounds like you have been pushing ai to much and making it hallucinate. Maybe take some time to read the docs understand weweb more rather then trying to use external tools to understand it.