We want something like a settings page that allows users to pick the experimental features they want enabled in their session. That way we don't interfere with users that don't want any experiments and we provide means to try the new stuff.

Should make sure that features can be supplied through URL and creating a URL (the "Share" button) includes the enabled features.

When a user signs out outside of Presentation Rules Editor, current user session will be invalidated on the server side and we will no longer be able to silently refresh user's auth token. When silent refresh fails, we should tell user that their session has expired and offer them to sign in again. We must make sure not to lose user's unsaved work in the process.

Currently silent sign-in callback is processed in a hidden iframe which effectively loads a second full instance of Presentation Rules Editor. A better solution would be to serve a specifically crafted html file which includes only the script necessary to process the sign-in result.

We are currently depending on oidc-client which is unmaintained since 2021. The suggested replacement is oidc-client-ts which is not only newer but also much smaller.

The Projects API has been replaced by the iTwins API. You should migrate your code to use the iTwins API as soon as possible.

Repro steps:

1. Open any iModel
2. Edit the default ruleset
3. Switch to "Browse iModels" tab
4. Switch back to "Ruleset Editor" tab

Result: The ruleset is reset to default.
Expected result: The ruleset is preserved when switching tabs or even iModels.

When "Submit Ruleset" is clicked and it takes a while to update content for the components, it impossible to know if that already happened or is still in progress. We should add some indication.

Bundle analyser shows that monaco-editor (~3MB) and iTwin.js (~6MB) libraries are concatenated into the same bundle.

We only need iTwin.js libraries to start connecting to an iModel, and while connecting, we can load monaco-editor bundle in parallel to speed up application startup.

When an error occurs, tell the user what happened and offer to retry or select another iModel.

Need a widget that shows problems encountered when handling given ruleset: non existing classes, invalid / deprecated attributes, etc.

@itwin/imodel-browser-react package has been unmaintained for quite a while and has become incompatible with recent iTwinUI-css versions. This package also introduces its own tile component which looks and acts differently from the one in iTwinUI-react. We chose to style all tile components in the app like imodel-browser-react does for consistency.

We need to write our own iModel browser that will allow users to search and open local, cloud, and demo iModels. All tile components in the app will be switched over to use iTwinUI-react implementation.

The V1 API is about to be turned off, need to switch to using V2. Docs: https://developer.bentley.com/apis/imodels/overview/#howtouseimodelsapiv2version

Investigate whether CSS is being minimised in production bundles, and if not, add a webpack plugin that does so.

Currently we are using Node.js 14.x on all release and build pipelines.

Need to make that available to Bentley internal users

At the moment SelectableInstance renderer doesn't work because the properties widget doesn't provide UnifiedSelectionContext