Sender | Message | Time |
---|---|---|
30 Sep 2023 | ||
then was telling me to add dyn | 21:08:37 | |
let me retry | 21:08:40 | |
its because you didnt change impl<T> to impl<T, E> | 21:08:48 | |
eh yeah maybe i forgot it mhm | 21:09:06 | |
you might be able to omit E entirely and do for Result<T, _> idk | 21:09:42 | |
or at least not include it in the ResultOpt<T> | 21:09:55 | |
it work for now I LOVE YOU | 21:13:33 | |
now it's late for me, so i'll continue fix code tomorrow, really thanks for help, i learnt a lot | 21:14:10 | |
-bow- | 21:14:19 | |
1 Oct 2023 | ||
21:30:44 | ||
Does anybody know whats the difference between a prop passed with ~ and ones passed without it? Like so:<MyComponent ~prop="foo" /> vs. <MyComponent prop="foo" /> the docs just say they are different from Component Properties: https://yew.rs/docs/concepts/html#specifying-attributes-and-properties but when I have a Property on a component it worked both with and without ~ as I expected | 21:30:45 | |
i believe it is js properties set for the dom element object | 22:02:27 | |
component properties (props) are different thing from those, as mentioned in the doc | 22:03:16 | |
ngl if that what it is (js properties/fields), and you have it working for components, then its kinda weird, possibly a bug | 22:05:57 | |
hmm, that's what I also thought at first but if I just add a prop that is not specified in a prop struct it also does not work. So regardless of the ~ you need the property specified in your component. | 22:20:48 | |
when trying the communication_child_to_parent example in yew and changing the custom on_clicked=... prop to ~on_clicked=... also did not change the behaivour of the example | 22:23:34 | |
2 Oct 2023 | ||
if the parser accepts the syntax for components, I don't think that's intended. It should make no difference there, though (but please use the syntax without ~) for elements, the syntax differentiates between attributes and properties | 00:57:54 | |
05:43:50 | ||
yew::virtual_dom::Key Why can't you build this from arbitary bvalues | 14:59:06 | |
20:07:59 | ||
3 Oct 2023 | ||
01:37:39 | ||
01:38:09 | ||
hi there, I've been looking at Yew 0.21 a little bit, and seems there are more breaking changes than was mentioned in the release notes, in particular regarding the html! macro. If I understand correctly, it used to accept any expression that could be turned into Html , which included anything that had a .to_string() (for instance, a chrono::DateTime ), but now it only accepts things that implement ToHtml , which doesn't seem to be implemented for nearly as many things as before... | 01:38:10 | |
basically, just wanted to check my understanding is correct | 01:38:28 | |
I guess the fix is to add a lot more .to_string() | 01:38:41 | |
04:14:21 | ||
06:52:43 | ||
Download main.rs | 06:52:44 | |
Hi there, I'm having trouble getting a basic use_state set up -- I tried to structure my code very similarly to the tutorial but am getting an error regarding IntoPropValue not being implemented. I've tried a bunch of variations and nothing seems to work: | 06:52:45 | |
Hit the character limit, but here's a link to the line where the error is pointed out: https://github.com/suttonbradley/clippers/blob/58a6ff91d813f3ab456361698bcdae1cc648a437/frontend/src/main.rs#L38 Thanks in advance for any help/suggestions 🙂 | 06:56:18 |