Component-agnostic APIs
No due date
22% complete
At the moment most of our APIs are tied to @itwin/components-react
package. This has the following drawbacks:
- Peer dependency on
appui
packages. - APIs can only be used or are only convenient to use with components from
appui
packages.
Need to provide component-agnostic APIs for all our components - this will allow:
- Drop
appui
peer dependencies (some may…
At the moment most of our APIs are tied to @itwin/components-react
package. This has the following drawbacks:
- Peer dependency on
appui
packages. - APIs can only be used or are only convenient to use with components from
appui
packages.
Need to provide component-agnostic APIs for all our components - this will allow:
- Drop
appui
peer dependencies (some may need to stay as simple dependencies, but that's much better than peer). - Consumers to use our APIs with components other than the ones in
appui
.