Iteration Release v6.1.0

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.

Releases

@finos/legend-application@5.0.0

Major Changes

• #1239 4dacea12 (@akphi) - BREAKING CHANGE: Restructured documentation registry, each documentation entry now can also relate to other documentation (referring to others by their keys). Contextual documentation registry is now simplified to become a map between context and documentation key. As a result, in LegendApplicationConfigurationData.documentation, contextualDocEntries now becomes contextualDocMap, also, in LegendApplicationPlugin, getExtraKeyedContextualDocumentationEntries() now becomes getExtraContextualDocumentationEntries(). Renamed LegendApplicationDocumentationEntryConfig to LegendApplicationDocumentationConfigEntry.

• #1239 4dacea12 (@akphi) - BREAKING CHANGE: Change LegendApplication contructor to take a LegendApplicationConfigurationInput<T extends LegendApplicationConfigurationData> to make it more scalable.

Minor Changes

• #1239 4dacea12 (@akphi) - Expose execution plan viewer component.

• #1239 4dacea12 (@akphi) - Support loading documentation regitry entries from an external source, e.g. documentation.registry: [{ url: 'https://legend.finos.org/resource/studio/documentation' }]; this config takes an additional flag simple when the endpoint is only just a JSON file and the server has a fairly relaxed CORS policy (Access-Control-Allow-Origin", "*"), e.g. documentation.registry: [{ url: 'https://legend.finos.org/resource/studio/documentation.json', simple: true }].

  Also, we have finalized the order of overriding for documentation entries. The later will override the former in order:

  • Natively specified: specified in the codebase (no overriding allowed within this group of documentation entries): since we have extension mechanism, the order of plugins matter, we do not allow overriding, i.e. so the first specification for a documentation key wins
  • Fetched from documentation registries (no overriding allowed within this group of documentation entries): since we have extension mechanism and allow specifying multiple registry URLS, we do not allow overriding, i.e. so the first specification for a documentation key wins
  • Configured in application config (overiding allowed within this group)

  We also provided an extension mechanism to specify required documentation entries. When we build the documentation registry, we will check these keys and any documentation keys configured in the contextual documentation map to ensure the application documentation show up properly for crucial use cases. Missing entries will trigger warnings.

Patch Changes

• #1240 7b5dfbee (@YannanGao-gs) - Add element path to element dropdown.

@finos/legend-graph@9.0.0

Major Changes

• #1239 4dacea12 (@akphi) - BREAKING CHANGE: Removed V1_getExtraSourceInformationKeys and AbstractPureGraphManager.pruneSourceInformation as we have refactored to do this more systematically. If you need to prune source information, you can still use MetaModalUtils.pruneSourceInformation, which is now configured to remove all fields with the suffix sourceInformation.

  BREAKING CHANGE: AbstractPureGraphManager.elementToEntity now takes an option: { pruneSourceInformation?: boolean } instead of a boolean flag to determine if it should prune the source information.

• #1236 ed3da137 (@akphi) - BREAKING CHANGE: Remove hashValue from PackageableElementReference and remove V1_transformElementReference.

Minor Changes

• #893 24ea81a8 (@gayathrir11) - Introduce extension mechanism consistently and exhaustively for class mapping

Patch Changes

• #1236 ed3da137 (@akphi) - Fix a regression where stubbed enum-value mappings are not properly detected (#1237).

@finos/legend-shared@4.0.0

Major Changes

• #1239 4dacea12 (@akphi) - BREAKING CHANGE: recursiveOmit() utility now takes a checker function instead of a list of property keys to prune.

@finos/legend-extension-dsl-diagram@4.1.0

Minor Changes

• #1239 4dacea12 (@akphi) - Support align and distribute spacing operators (e.g. align left, align right, distribute spacing horizontally etc.) when selecting multiple class views.

@finos/legend-studio@10.2.0

Minor Changes

• #893 24ea81a8 (@gayathrir11) - Introduce extension mechanism consistently and exhaustively for class mapping

@finos/legend-extension-dsl-text@3.0.4

Patch Changes

• #1236 ed3da137 (@akphi) - Test.type is now optional, when not provided, we will render the content as plain text.

@finos/babel-preset-legend-studio@2.0.3

@finos/eslint-plugin-legend-studio@2.0.2

@finos/legend-art@2.0.3

@finos/legend-dev-utils@2.0.2

@finos/legend-extension-dsl-data-space@3.0.4

@finos/legend-extension-dsl-persistence@2.0.4

@finos/legend-extension-external-format-json-schema@2.0.4

@finos/legend-extension-external-language-morphir@2.0.4

@finos/legend-extension-external-store-service@3.0.4

@finos/legend-extension-mapping-generation@2.0.4

@finos/legend-graph-extension-collection@2.0.4

@finos/legend-model-storage@2.0.3

@finos/legend-query@3.0.4

@finos/legend-query-app@6.1.0

@finos/legend-server-depot@2.0.3

@finos/legend-server-sdlc@3.0.3

@finos/legend-studio-app@6.1.0

@finos/legend-studio-extension-management-toolkit@2.0.4

@finos/legend-studio-extension-query-builder@2.0.4

@finos/legend-taxonomy@4.0.4

@finos/legend-taxonomy-app@6.1.0

@finos/legend-tracer-extension-zipkin@2.0.3

@finos/legend-manual-tests@2.0.4

@finos/legend-query-deployment@6.1.0

@finos/legend-studio-deployment@6.1.0

@finos/legend-taxonomy-deployment@6.1.0