updated * to itwinui 3 #141
Conversation
| "@itwin/itwinui-icons-react": "^2.2.0", | ||
| "@itwin/itwinui-react": "^2.12.18", | ||
| "@itwin/itwinui-icons-react": "^2.9.0", | ||
| "@itwin/itwinui-react": "^3.16.5", |
There was a problem hiding this comment.
i think itiwnui would need to become a peer dep
There was a problem hiding this comment.
updated all packages in monorepo
There was a problem hiding this comment.
i dont see this as a dev+peer dep
There was a problem hiding this comment.
should also use the latest version, 3.17, to add support for the theme bridge
There was a problem hiding this comment.
i dont see this as a dev+peer dep
its used in prod implementation in this package. i could add it as a peer but i dont think anything else here would have the same subdep on itwinui-react? why in dev if needed in prod?
There was a problem hiding this comment.
should also use the latest version, 3.17, to add support for the theme bridge
updated to latest 3.17.3
|
Can we bump the priority on this one, since iTwin for Desktop wants to upgrade to itwinui's theme bridge and according to their wiki all of the dependencies should be on v3 and we depend on imodel-browser-react pkg |
aruniverse
left a comment
There was a problem hiding this comment.
plz review existing comments?
is there a need to update every single pkg in this monorepo for your app?
| "@itwin/itwinui-icons-react": "^2.2.0", | ||
| "@itwin/itwinui-react": "^2.12.18", | ||
| "@itwin/itwinui-icons-react": "^2.9.0", | ||
| "@itwin/itwinui-react": "^3.16.5", |
There was a problem hiding this comment.
i dont see this as a dev+peer dep
| "tslib": "^2.6.2", | ||
| "typescript": "^4.2.3" | ||
| "typescript": "^4.2.3", | ||
| "@testing-library/dom": "~10.4.0", |
There was a problem hiding this comment.
lets alphabetize our deps
moved the '@' prefixed deps
| @@ -13,7 +13,7 @@ | |||
| "@itwin/delete-imodel-react": "^2.0.0", | |||
| "@itwin/delete-itwin-react": "^2.0.0", | |||
| "@itwin/imodel-browser-react": "~2.3.1", | |||
There was a problem hiding this comment.
shouldnt these (pkgs within the monorepo) be using the workspace:* protocol?
There was a problem hiding this comment.
shouldnt these (pkgs within the monorepo) be using the
workspace:*protocol?
that would make sense, however workspace does not appear to be configured in this repo perhaps that change should be in its own pr
| "@itwin/itwinui-icons-react": "^2.2.0", | ||
| "@itwin/itwinui-react": "^2.12.18", | ||
| "@itwin/itwinui-icons-react": "^2.9.0", | ||
| "@itwin/itwinui-react": "^3.16.5", |
There was a problem hiding this comment.
should also use the latest version, 3.17, to add support for the theme bridge
| @@ -11,28 +11,24 @@ import React, { forwardRef } from "react"; | |||
| export const IModelGhostTile = forwardRef<HTMLDivElement>((props, ref) => { | |||
| return ( | |||
| <ThemeProvider ref={ref} theme="inherit" {...props}> | |||
There was a problem hiding this comment.
if the plan is to use the theme bridge, then wouldnt you need to expose that for every single component that you wrap with theme provider?
would it make more sense to not wrap anything in theme provider, and expect the host/parent app to do so instead?
There was a problem hiding this comment.
if the plan is to use the theme bridge, then wouldnt you need to expose that for every single component that you wrap with theme provider?
would it make more sense to not wrap anything in theme provider, and expect the host/parent app to do so instead?
i think it would be fine given the theme is set to inherit?
https://itwinui.bentley.com/docs/themeprovider#inheritance
i only needed imodel-browser updated. its been some time but i recall having some issues updating only that package, and figured they would all need to be updated eventually anyway so might aswell. i think updating the whole repo is also the goal of work item |
|
closing in favor of #144 |
@aruniverse #144 is only concerned with updating |
I wouldn't say abandon, but if we have no consumers asking for iTwinUI v3 versions of it, then we can defer it |
|
OpenSite+ is not using any of the other packages in this repo |

UPDATE
Note
would make some suggestions, pending state at merge, separate issues can be created