-
Notifications
You must be signed in to change notification settings - Fork 37
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
Refining the grammar of the LengthComparison
#221
Conversation
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.
I really like this PR, because it simplifies the language. I want this PR to be in 1.0, because to go back and change something like this after we've released 1.0 is a horrible idea.
However, before I click 'approve', I want more people who are currently engaged in writing implementations to say that they agree, since this does force them to go back and change things that are already working for a mere syntax improvement.
I'm going to 'request review' on a few of them.
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.
To me this seems OK, and I'd be happy to have it merged ASAP.
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.
(I'm making a blocking "request changes" review here, as I will urge others to approve the change and want to avoid accidental merging the changes until a few of those are in.)
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.
Looks good to me (as long as we ASAP update the grammar in optimade-python-tools
😉 ).
Thanks @fekad!
For me the change to the grammar is ok to be made - I'm not approving since anyway I see there are other changes requested, but happy to do if needed when all changes have been taken care of. |
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.
Some clarifications desired. Mainly for the sentence I put in a suggested change for. Otherwise, I would say this is good-to-go.
Co-Authored-By: Casper Welzel Andersen <43357585+CasperWA@users.noreply.github.com>
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.
One reformulation, otherwise good to go.
Co-Authored-By: Rickard Armiento <gitcommits@armiento.net>
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.
Cheers @fekad. And thanks for patiently responding to our (my) many questions 👍
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.
Great!
Update from v0.10.0: Implement Materials-Consortia/OPTIMADE#221
Update from v0.10.0: Implement Materials-Consortia/OPTIMADE#221
Update from v0.10.0: Implement Materials-Consortia/OPTIMADE#221
Update from v0.10.0: Implement Materials-Consortia/OPTIMADE#221
Update from v0.10.0: Implement Materials-Consortia/OPTIMADE#221
Update from v0.10.0: Implement Materials-Consortia/OPTIMADE#221
Closes #199
This PR has been made according to a previous issue (#199).