Skip to content

Releases: iTwin/presentation

@itwin/[email protected]

30 Oct 10:56
8c7a306
Compare
Choose a tag to compare

Minor Changes

  • #740: Define type and exports attributes in package.json.

    The change moves this package a step closer towards dropping CommonJS support - it's now transpiled from ESM to CommonJS instead of the opposite.

    In addition, the exports attribute has been added to package.json to prohibit access to APIs that are not intended to be used by external consumers.

Patch Changes

@itwin/[email protected]

30 Oct 10:56
8c7a306
Compare
Choose a tag to compare

Minor Changes

  • #747: KoQ and numeric editor improvements.

    • ReadOnly properties now open a disabled input in property grid.
    • KoQ input placeholder is now determined by initial value if one exists.
    • Selecting/clicking a numeric or KoQ input will select all the text.
  • #739: Replaced react-select with iTwinUI's ComboBox.

    • The number of select options is limited to 100. When more items exist, a non-selectable option is displayed at the bottom of the list, prompting users to provide an items filter. Previously, additional pages of select options was loaded when user scrolled to the bottom of the list.
    • Deprecated PortalTargetContext. It is no longer needed.

    This affects PresentationInstanceFilterBuilder and NavigationPropertyEditor components.

  • #754: Define type and exports attributes in package.json.

    The change moves this package a step closer towards dropping CommonJS support - it's now transpiled from ESM to CommonJS instead of the opposite.

    In addition, the exports attribute has been added to package.json to prohibit access to APIs that are not intended to be used by external consumers.

@itwin/[email protected]

15 Oct 06:35
abbef0c
Compare
Choose a tag to compare

Patch Changes

  • #730: Fix provider returned by createHiliteSetProvider in some cases not caching class hierarchy check results, resulting in duplicate checks for the same classes.

@itwin/[email protected]

15 Oct 06:35
abbef0c
Compare
Choose a tag to compare

Minor Changes

  • #711: Increased the speed of hierarchy filtering with large number of filtered paths.

    Amount of paths Before the change After the change
    500 960.18 ms 233.65 ms
    1k 2.29 s 336.81 ms
    10k 232.55 s 2.17 s
    50k not tested 13.45 s

    In addition, changed NodeParser (return type of HierarchyDefinition.parseNode):

    • It now can return a promise, so instead of just SourceInstanceHierarchyNode it can now also return Promise<SourceInstanceHierarchyNode>.
    • Additionally, it now accepts an optional parentNode argument of HierarchyDefinitionParentNode type.

@itwin/[email protected]

15 Oct 06:35
abbef0c
Compare
Choose a tag to compare

Patch Changes

@itwin/[email protected]

04 Oct 10:36
79bcbf1
Compare
Choose a tag to compare

Major Changes

  • #727: 1.0 release.

    The APIs are now considered stable and ready for production use.

Patch Changes

@itwin/[email protected]

04 Oct 10:36
79bcbf1
Compare
Choose a tag to compare

Major Changes

  • #727: 1.0 release.

    The APIs are now considered stable and ready for production use.

@itwin/[email protected]

04 Oct 10:36
79bcbf1
Compare
Choose a tag to compare

Major Changes

  • #727: 1.0 release.

    The APIs are now considered stable and ready for production use.

Patch Changes

@itwin/[email protected]

04 Oct 06:37
7d4d584
Compare
Choose a tag to compare

Patch Changes

  • #720: Fixed iModel hierarchy provider returning unfiltered nodes after setting the hierarchy filter in certain scenarios.

    The situation could happen when a new hierarchy filter is set during an ongoing nodes request. Then, requesting nodes immediately after setting the filter could return nodes from the previous request.

    The change also slightly changes what happens with ongoing requests when hierarchy provider's internal state is reset: provider is disposed, the imodelChanged event is raised or hierarchy filter is set. Previously, it would continue handling all ongoing requests and return a valid result. Now, it will stop ASAP and return an empty list.

@itwin/[email protected]

04 Oct 10:36
79bcbf1
Compare
Choose a tag to compare

Major Changes

  • #727: 1.0 release.

    The APIs are now considered stable and ready for production use.

Patch Changes