I wanted to report an issue I encountered in Backendless related to two reusable components (RC1 and RC2) that are interconnected because one was created using the clone option. Both components use the Tree Select component, and I implemented two custom classes to make the label behave like an outlined variant label (since the Tree Select doesn’t offer this option by default).
The expected behavior is that when the Tree Select component is filled, the label (which I’ve implemented using a Text component) should “fly” to the top. However, when I applied the specific class to make the label “fly” in RC1, the expected effect didn’t happen in RC1. Instead, the effect applied to RC2.
After trying several approaches, and reviewing the codeless, I ended up adding a new Text component to RC1, and that resolved the issue. This makes me wonder if the clone operation might be creating some kind of link between RC1 and RC2, which could explain the unexpected behavior.
Additionally, what’s even more puzzling is that this functionality had been working fine and was previously validated. However, when I opened the page yesterday, i found this issue. Honestly, i can´t explain this, maybe i did something…
This reminds me of a similar issue I encountered earlier with modals. When I copied and pasted a modal, some of the properties of the child modal were affected whenever I changed the parent modal, and vice versa. Again, it seems that some kind of link is kept between related modals…
I wanted to ask if this issue has been identified or if other users have reported similar problems. It “seems” like there might be an underlying issue with the clone operation or component duplication in Backendless.
I’d appreciate any insights or suggestions you might have regarding this.
I was working on creating the requested test container (page TestContainer based on the page where I had issues with the RCs) when I realized that I’m now unable to preview the page.
Please disregard the “preview page” issue.
I managed to resolve it.
Regarding the other issues, I’ve created the page TestContainer in my app, which contains “copies” of the 2 reusable components in question (please note that the current version is working fine).
I’ve also added two modals in case you’d like to test those as well.
Thank you for following up. Unfortunately, I don’t have additional details to provide. The issue occurred with modals and reusable components (RCs). What I can share is that the problem was resolved only when I created a new modal from scratch (without copying, pasting, or cloning) and added a new text component to one of the RCs.
