Replies: 2 comments 5 replies
-
Yeah I hear ya. This nuance is mentioned in the docs, but I agree it could be clearer.
Could maybe add more examples in the docs, and/or call out this use case with the form builder explicitly. But I feel like ideally we'd make re-reading the docs unnecessary. Maybe we can implement a custom stream action that'll include the solution in an error message? Very much in line with #61 |
Beta Was this translation helpful? Give feedback.
-
#64 merged! Thanks for flagging this. It's easy to forget what it's like to use the library for the first time. |
Beta Was this translation helpful? Give feedback.
-
Take this case:
On the server-side response, you need to use:
The
comment_
prefix here is easy to miss andI had to inspect the HTML & turbo stream response to see why the options were not being populated.Any good ideas how this could be simplified? Rails makes the ID on the generated field automatically, so it's easy to forget that or miss entirely if you're unaware of that feature.
I don't know a great solution for this, but shared context would be nice to make this feel more intuitive.
Or maybe the docs just need more examples with these nuances.
Beta Was this translation helpful? Give feedback.
All reactions