-
-
Notifications
You must be signed in to change notification settings - Fork 83
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
Unpin wasm-bindgen
version
#185
Conversation
This looks promising, thanks! Did you close it on purpose? |
Yes, I ran the tests and was a bit overwhelmed. 😃 |
In the tests, this appearead to be the only error:
You should just need to add an import for The CI check seems to be failing due to |
Like I said the warnings are not the problem but
Is that failing because it enables exclusive features together? Like |
Fortunately, none of the tests run as part of CI use all features. Reproducing lines here: - name: Run tests (general)
run: cargo test --features math,docs,ssr
- name: Run tests (axum) use_cookie
run: cargo test --features math,docs,ssr,axum --doc use_cookie
- name: Run tests (axum) use_locale
run: cargo test --features math,docs,ssr,axum --doc use_locale
- name: Run tests (actix) use_cookie
run: cargo test --features math,docs,ssr,actix --doc use_cookie
- name: Run tests (actix) use_locale
run: cargo test --features math,docs,ssr,actix --doc use_locale
That's my guess. The CI tests those both separately, so I think it only really needs to pass for the |
@SleeplessOne1917 Is correct. It can't work with all features enabled because that would run client and server code at the same time. |
src/utils/use_derive_signal.rs
Outdated
@@ -12,7 +12,7 @@ macro_rules! use_derive_signal { | |||
pub fn $name<V $(, $( $type_param ),* )? >(value: V) -> Signal<$return_type> | |||
where | |||
$inner_signal_type $(< $( $inner_type_param ),+ >)?: Send + Sync, | |||
V: Into<Signal<$inner_signal_type $(< $( $inner_type_param ),+ >)?>> $(, $( $type_param $( : $first_bound $(+ $rest_bound)* )? ),+ )? | |||
V: Into<ReadSignal<$inner_signal_type $(< $( $inner_type_param ),+ >)?>> $(, $( $type_param $( : $first_bound $(+ $rest_bound)* )? ),+ )? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure about this one. Is this type constraint too tight? Should not be allowed to write to signals in derives, no?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, this should definitely stay Signal
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Then I'll add type annotations in the example.
The remaining warnings are the deprecation hints that #187 fixes. |
5665a17
to
1bcda56
Compare
Thanks! |
Unpin
wasm-bingen
to be compatible withleptos-0.7.0-rc1
. See leptos-rs/leptos#3186.Fixes #176