-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
improve Legend Query
and Legend Taxonomy
performance
#1295
Conversation
🦋 Changeset detectedLatest commit: dcbb459 The changes in this PR will be included in the next version bump. This PR includes changesets to release 33 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Codecov Report
@@ Coverage Diff @@
## master #1295 +/- ##
=======================================
Coverage 41.66% 41.66%
=======================================
Files 1158 1175 +17
Lines 52393 52441 +48
Branches 11948 11880 -68
=======================================
+ Hits 21827 21849 +22
- Misses 30499 30524 +25
- Partials 67 68 +1
|
395c7c1
to
6b2a9fd
Compare
397e49f
to
47685cf
Compare
Added a new query creation mode from data space, this will mode can be accessed from `Legend Query` using the `url pattern` | ||
|
||
``` | ||
/query/extensions/{groupId}:{artifactId}:{versionId}/{dataSpacePath}/{executionContext}/{runtimePath}? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why is runtimePath an option here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since people are picking the execution context
of a data space which already specified with a default runtime
. When people pick another option other than the default runtime
, we will put that in the url with this param
Updated #936 to reflect some of the work done in this PR |
@MauricioUyaguari This potentially also fixes #1092 so we should check that with some substantial-sized graphs |
* query-builder: remove the link between query setup and editor * update custom eslint rules post ESM import upgrades * query builder: add new simplified graph analytics * docker: update finos/legend-shared-server to avoid CVEs * query: optimize service execution query loading flow * cleanup usage of depot client methods * query: optimize create query from mapping and runtime flow * query builder: temporarily hide error indicator for incompatible mapping * query builder: relax mapping runtime setup checks * reorder parameters of execution-related methods in AbstractPureGraphManager * tracer: remove usage of terminology 'span' * fixes tests and cleanup post rebase * data space: use engine analytics API for loading up dataspaces * legend-query: create QueryEditorStore and simplify LegendQueryStore * legend-query: polomorphize QueryEditorStore * move getExtraApplicationPageRenderEntries() to @finos/legend-application * query: new query creation mode from data-space * add and update changeset * query: make query editor URL more consistent * use HOC for store provider wrapper components * taxonomy: use data space analytics API for loading * bump dependencies * minor fixes
Summary
Legend Taxonomy
andLegend Query
- closes Feature request: Improve UX when loading dataspaces #936useQuerySetupStore
->useSetupStore
LegendQuery
LegendQueryEditorStore
and movegraphStateManager
into that fromLegendQueryStore
Legend Query
testss post editor store refactoringGAV coordinate ({groupId}:{artifactId}:{versionId})
instead of{groupId}/{artifactId}/{versionId}
formLegend Taxonomy
use the new data space analytics APIengine
- fix problem with dataspace analytics endpoint legend-engine#807depot
client to supportversion aliases
depot
client methods to make the code more organizedmap
to ending withindex
to better reflect their usagecontextual documentation
execution
-related methods inAbstractPureGraphManager
to make them more consistent with the rest of the methodsHow did you test this change?