-
Notifications
You must be signed in to change notification settings - Fork 352
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
0.13: Add Dynamic Queries section #895
0.13: Add Dynamic Queries section #895
Conversation
The query transmutes that were added in that pr are immediately useful. Probably should be a separate section. |
@hymm I like the idea of writing a section in query transmutes. I could have used them in the past. |
Co-authored-by: Félix Lescaudey de Maneville <[email protected]>
I'll try and write something up for that. |
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.
Minor grammar changes and such, otherwise LGTM.
* Create an [editor with remote capabilities]. | ||
* And those are only what people came up with _before_ the 0.13 release! | ||
|
||
We expect third party crates to provide convenient wrappers around the `QueryBuilder` API. |
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.
This sentence could be probably be better integrated into the start of the paragraph above.
Co-authored-by: TrialDragon <[email protected]>
For #891 announcement post.
I also added a subsection on relations, since it's a primary motivator for dynamic queries.
But, it feels like it's just too much for this section. Maybe push it to the "what's next?" section… Could use it as a synthesis for all the changes that brings us closer to relations.
@james-j-obrien, @jakobhellermann, @Suficio, or anyone. Please tell if anything is wrong or misleading.
I think I got it alright: context + motivation in two sentences, despite the subject being complex and not immediately useful to end users. Then spin it in a way that is interesting (I think) thanks to the amazing projects people are already building on top of dynamic queries, since those projects are useful for end users.