Open craxal opened 1 year ago
Let's please make sure to discuss pros/cons as a team before doing this work....I don't recall this being brought up before.
Let's pick this up once we are investigating react dialogs or have a package which is react only.
I believe we discussed that it's better just to keep things together. Since we're weening off Knockout, there's not much value in creating a whole new package just for Knockout things we won't be using for very long.
We can use this item to track the migration from React to Knockout and close it once Knockout has been phased out.
Delivering both Knockout and React components in the same package creates unnecessary dependencies in extensions that only use components for one framework or the other. It also creates unnecessary churn when something needs a fix or update.
React components should be moved to a separate package, such as
@storage-explorer/react
.We could consider creating a family of packages, each containing an individual component and one package that exposes everything, as is done for the Fluent UI framework.