You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Due to the natural evolution of the two codebases, the monarch-ui currently does a lot of json manipulation after fetching data from Biolink. Ideally, this would be minimized and biolink would provide the ui a closer representation of what is needed for our views.
Examples:
Node pages make two calls to Biolink - neighbors, and {type}/{id}, followed by a lot of data manipulation - see Node.vue
Calls to getNeighborhood are followed by lot's of data munging - see getNeighborhood, this reminds me of "fetchClassInfo" from our legacy app
Operating on BBOP Graphs browser side, see getNeighborhood above and BBOPGraphUtils.js
Due to the natural evolution of the two codebases, the monarch-ui currently does a lot of json manipulation after fetching data from Biolink. Ideally, this would be minimized and biolink would provide the ui a closer representation of what is needed for our views.
Examples:
The text was updated successfully, but these errors were encountered: