-
Notifications
You must be signed in to change notification settings - Fork 192
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
Docs: Move in section on QueryBuilder to How-To #4080
Docs: Move in section on QueryBuilder to How-To #4080
Conversation
I'm still not 100% happy with the current text, but I figured it would be good to first get some feedback on the content. Some open questions in this regard:
|
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.
Thank you very much! I've provided some comments and suggestions. I suggest that we address those first and then we revisit your concerns.
I was just discussing with @mbercx and we think the current page for the |
I agree notwithstanding that some of the content would better be placed within the reference chapter (see related comments). |
Thanks @csadorf and @sphuber for the comments! To distill the how-to, I was thinking of limiting the sections to the following:
And moving the other sections to the topics, perhaps under "advanced querying"? For the reference section, do I simply make a |
aa404e6
to
7252417
Compare
I think I need to see this to be really able to make a call. Maybe give it a shot and we see how it pans out?
Since the |
I think this has the right length and scope now. I am really happy with the section now. |
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.
Thanks a lot @mbercx . Really like the structure, scope and length. Just have some suggestions. Also do not forget to make clear here that we are only moving part of the existing docs, that is rephrased as well, and not all the content that is removed is addressed here. But you will do this in a separate PR for another issue. Would be good to link it once we decided which issue it will be
02dd9ad
to
b502de0
Compare
Thanks again @sphuber and @csadorf for the suggestions and discussion! A few notes:
|
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.
Honest to god, these are the last two comments :) and then we can merge
docs/source/howto/data.rst
Outdated
@@ -404,4 +659,4 @@ Notice that we haven't specified any port in the URLs since Apache listens conve | |||
|
|||
.. _#3996: https://github.com/aiidateam/aiida-core/issues/3996 | |||
.. _#3997: https://github.com/aiidateam/aiida-core/issues/3997 | |||
.. _#3998: https://github.com/aiidateam/aiida-core/issues/3998 | |||
.. _#3998: https://github.com/aiidateam/ |
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 is an accidental change I imagine? You can restore this and actually remove the link for 3996, which is the one this PR solves
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.
Yes, this was accidental. I must have gotten a little overzealous while slimming down the section. ^^
docs/source/howto/data.rst
Outdated
|
||
qb = QueryBuilder() | ||
qb.append(CalcJobNode, tag='calcjob') | ||
qb.append(Int, with_incoming='calcjob', project=['id', '*', 'attributes.value']) |
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.
Just wondering: projecting both the instance and separate values might not make the most sense in most cases, as you can always get those properties from the instance once loaded. Note sure if it matters here, or if this slightly weird example may cause some confusion
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.
Fair point! The idea was to introduce project='*'
to another query to show that you can use '*'
like any other projection. I've moved this concept to the next query example.
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.
Perfect ! 👍
Promises Made - Promises Kept 😉 Thanks @mbercx ! |
Move in the sections on the `QueryBuilder` to the How-to section called "Finding and querying for data" The original text was too extensive for the purposes of the How-to and so it has been split in two. The detailed information on advanced queries will be added in another PR in the section "Topic - Database". The text for this How-to has been adapted from the original text with significant changes in the structure and simplifying the examples. Here wherever possible they use the `ArithmeticAddCalculation` for consistency with other sections and tutorials. The new structure is as follows: * Selecting entities * Retrieving results * Filters * Relationships * Projections
Fixes #3996
Move in the sections on the
QueryBuilder
to the 'Finding and querying for data' How-to of the revamped documentation.Changes quite a bit of the section on the appender method:
ArithmeticAddCalculation
process.The section on the
queryhelp
has been largely left 'as is', save for the introduction and some reformatting along the new style guidelines.