Hi Alban,
We allow duplicate icons to exist to prevent errors when base models are merged with the work model. In the case you would have a base model containing icons, these icons would be merged into your work model. May you already have this icon present in your work model, the merging cannot detect that by looking at the icon name, but can only determine it by looking at the underlying identity value; which is only equal if the icon came from the base model and was not uploaded directly into the work model.
There's a validation in place to detect duplicate icons based on the icon name to notify developers about them. Does this help out?
Hi Alban,
We allow duplicate icons to exist to prevent errors when base models are merged with the work model. In the case you would have a base model containing icons, these icons would be merged into your work model. May you already have this icon present in your work model, the merging cannot detect that by looking at the icon name, but can only determine it by looking at the underlying identity value; which is only equal if the icon came from the base model and was not uploaded directly into the work model.
There's a validation in place to detect duplicate icons based on the icon name to notify developers about them. Does this help out?
Hi Mark,
Very clear answer