[Description]
The problem appears when an primary asset located in the root of an analysis
When we click multiple times and move it a little bit (almost at the same position), the asset can be linked accidentally to itself. Means its root and parent asset will have the same id as asset instance id.
E.g. instance with id = 1, can have parent_id = 1 and root_id = 1.
[Solution]
As a solution we should prevent such situation happening on Backend side by validating if the asset is going to be linked to itself and raise an error.
The second point is to prevent the circular fetching issue by changing this method for already broken instances.
Try to prevent this on Frontend by might be locking the UI while loader is not completed or another solution.
jfrocha
commented
2 years ago
[Description] The problem appears when an primary asset located in the root of an analysis When we click multiple times and move it a little bit (almost at the same position), the asset can be linked accidentally to itself. Means its root and parent asset will have the same id as asset instance id. E.g. instance with id = 1, can have parent_id = 1 and root_id = 1.
[Solution]