-
Notifications
You must be signed in to change notification settings - Fork 105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Possibly redundant functionality #123
Comments
My feelings with regards to Wasm support is to provide the framework-agnostic basic building blocks so that other libraries can be build on top of it. The problem with integrating e.g. So I would leave the level of Wasm support as it is at the moment i.e. just provides some convenient bindings to In terms of examples, I'd definitely like more examples of usage within other frontend frameworks. The only reason that the only example is for I think there is space in the ecosystem for separate libraries such as yours which specialise for different frontends. |
Makes sense to me. Then the maintenance of the yew-specific support/examples could be moved to my crate and I set up some CI tests on my side to assure future compatibility. |
A few days ago I wrote and released a crate featuring a yew component wrapper that uses your library. Now I noticed you also just recently extended the wasm support and added examples for yew.
I wonder if it would make sense integrating this crate into your repo, or if we could move both repos to a joint github org?
The text was updated successfully, but these errors were encountered: