Then select the new target ApplicationSystemTypeCatalogue
Expected Behaviour
The results for ApplicationSystemTypeClassified -> ApplicationSystemTypeCatalogue are shown, since this is the currently shown path.
Current Behaviour
First, nothing is shown while both SPARQL queries are waiting for the answer of the server.
Then, the answer for ApplicationSystemTypeClassified -> ApplicationSystemTypeCatalogue is shown (probably because the SPARQL query is much shorter). This is the expected behaviour.
After a short time, the results for ApplicationSystemTypeClassified -> EnterpriseFunctionClassified are shown, since the longer and more complex SPARQL query needed more time to be completed and is now shown, disregarding the new path.
Possible solutions
Abort the first SPARQL query/ignore the result if it does not match the currently selected path -> probably the most expected option, I would suggest this one as the final solution
Let both SPARQL queries run and when results are in, select the path matching the result -> this could confuse users, I don't think this is a good idea
Make selecting different nodes impossible -> would make the application feel unresponsive, but better alternative than (2) if (1) turns out to be not implementable easily
Steps to reproduce (example)
Expected Behaviour
The results for ApplicationSystemTypeClassified -> ApplicationSystemTypeCatalogue are shown, since this is the currently shown path.
Current Behaviour
First, nothing is shown while both SPARQL queries are waiting for the answer of the server. Then, the answer for ApplicationSystemTypeClassified -> ApplicationSystemTypeCatalogue is shown (probably because the SPARQL query is much shorter). This is the expected behaviour.
After a short time, the results for ApplicationSystemTypeClassified -> EnterpriseFunctionClassified are shown, since the longer and more complex SPARQL query needed more time to be completed and is now shown, disregarding the new path.
Possible solutions