Ben Polinsky
Ben Polinsky
Clarify API support policies re: security patches (latest minor version).
No previous versions are displayed
Page content to review - the mobile app page is especially incorrect. - https://www.itwinjs.org/learning/tutorials/develop-web-viewer/ - https://www.itwinjs.org/learning/tutorials/develop-desktop-viewer/ - https://www.itwinjs.org/learning/tutorials/develop-agent/ - https://www.itwinjs.org/learning/writeaninteractivemobileapp/
#### Feature The iTwinUI Header allows consumers to add links via a `breadcrumbs` prop. This displays the menu items with carets pointing to the next item to the right, making...
After an external repository's (appui/presentation/etc) docs are built, a docs release should be triggered. As long as the external build uses the latest published artifacts from each repository, the external...
When extensions were first developed, it was thought that using the `@beta` jsdoc tag to represent an early-release API would be confusing, as the core library had many other APIs...
Reproduction: - Open the itwinjs-core library in vscode. - Open a typescript file under core/common. - Restart the eslint server (Open command palette and type/select "restart eslint server") - Wait...
We're currently hard-coding a "Blank Connection Name" string - we should expose this as an optional prop.
Start apps/web-viewer-test. Error appears: ERROR in [eslint] Plugin "react" was conflicted between "package.json » ../../../common/scripts/.eslintrc.ts.json » ./.eslintrc.ts.base.json » plugin:react/recommended" and "BaseConfig » .../source/viewer/common/temp/node_modules/.pnpm/eslint-config-react-app@****
We should write playwright tests (I see no reason to reach for Cypress at this point) for the various test-viewer apps. We can run the tests in CI and catch...