r.ramalho

Same problem here, is there any known workaround ?! Thanks

Hi, @EmilStenstrom exactly the problem and pattern I tried to describe, I wanted to avoid having having templates for both components (fragments) and a component pages (full html pages), in...

@EmilStenstrom Exactly the idea and cenario i tried to convey, no need to reload: resources, footer, navbar and other shared elements, only the main frame content needs to change most...

Hi @EmilStenstrom I also tought about something along those lines, currently i am doing it like this, in case it helps anyone. Might need to be changed a little bit...

Hi @JuroOravec To provide some additional context, in my project i have a base template that renders both a page header (navbar) and page body, where the page body is...

Hi, @JuroOravec thank you. The UI is just regular bootstrap 5 with some customization to the default styles, each dialog is a django component view, the get method will retrieve...

Hi @JuroOravec, In my utilization components do always remain valid HTML, I don't really use the "data-djc-id-" attribute but the concept is the same as your describe, every component has...

@JuroOravec Every ID is unique, at least in practice, generation of repeated ID's can theoretically ocurr but that is outside of the scope of this matter.. when I say invalid...

@EmilStenstrom mostly in tune with my toughs, keeping it simple. @JuroOravec if you picture the components and their relationship's as a tree structure then a refresh of the root node...