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
trunk test #20
Comments
Are there any plans to go further with this discussion? |
I've been playing around with testing without wasm-pack in yewstack/yew#2528.
We would need to ask users to ensure that their |
I took a shot at implementing it but there's design discussion left to be done:
|
Thanks for trying out to implement this. I think this is a rather big change, so I'll go ahead and implement this. Regarding the issues you faced, I think we can solve most of them rather easy. Easy to solve
Problematic
|
It seems that |
abstract
Lots of discussion to be had here. The main idea is that we want a
trunk test
command which will do the right thing in terms of running unit tests, integration tests &c.A few ideas were being tossed around on the Yew community Discord. Right now, I am definitely leaning towards leveraging
wasm-pack test
as much as possible. It already handles a lot of the heavy lifting.Currently, this issue is in discussion phase. We need to determine what would be best for users.
The text was updated successfully, but these errors were encountered: