We have different people working in different containers, creating re-usable components in one container which we can then get into another container by using copy/paste in the components directories for the containers in the file system.
This works fine except there are annoying warning messages in the browser console along the lines of:
Component with uid: ‘xyze588d514efcee5e0d217a72678a99’ already registered for another node!
Is this because of the duplication of component uid when copying reusable components across containers? Is there a way to stop these annoying warnings?
Renaming the component(s) in the file system breaks things, so we can’t seem to do that. This is also somewhat annoying — it would be nice to be able to identify a component by just looking at its name.
That happens when you have 2 or more instances of one reusable component on the scene. Unfortunately, for now we can’t do anything to hide it, but you could create a filter for that in your dev tools.
Also, we have plans to make some changes that will remove this warning.
This is also somewhat annoying — it would be nice to be able to identify a component by just looking at its name.
UI Builder does not provide the possibility to manage something through files. When you move files manually and something will be broken - it’s not our responsibility.
OK, we will just ignore the warnings in the dev console for now
Using copy/paste in the file system seems to be the only way to be able to get re-usable components from one container into another (as opposed to having to build everything from scratch again). Or is there another way?
The copy/paste in the file system method is also a way to make copies of a page from one container to another. Or is there another, better way?
We really do have to have different people working in different containers because when 2 (or more) people are working on things in the same container, there are conflicts where one person overwrites another persons work, and there’s no way to “merge” code. Let me know if there are better ways for us to work as a team and thank you for all you do
Different containers it’s literally different production apps(don’t be confused with Backendless apps), so yes. We don’t look for the ability to migrate something between containers for now. But, since you ask for that we will discuss it with our development team. No promises, but we will look into it again.
seems to be the only way to be able to get re-usable components from one container into another
You could publish your component to the marketplace, and install them in a second container.
Here is an instruction. But it takes time while our developer approves it.
Unfortunately, we can’t offer you a silver bullet for your need.
Understood. The “publish to marketplace” is not an option at all since it is not possible to publish a “normal” reusable component — only “custom” component with React/JS code. Also having to wait for approval, and making the entire Backendless community look at various specialized components would be crazy.
Our biggest problem (and I know we are not alone with this) is that it’s not feasible for different team members to work on the same application at the same time, because work gets overwritten and lost. That’s because Backendless gets conflicting information about what to save to the server when there are multiple browsers accessing the same app. But working in different containers in our app is OK. However, then there is no way to copy components, pages, extensions from one container to the other, so we have to use the file system (as suggested by the Backendless support — see here and here)
If you know of a better way for teams with more than one person to work on the same application simultaneously, please let me know
Copying files is a workaround, and we just can’t guarantee that it will work properly.
As for the marketplace - your opinion is reasonable, just want to correct one little thing - it’s possible to publish reusable components, not only custom.
