-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Support Postgres POSIX regex operators close #4317 #6172
Support Postgres POSIX regex operators close #4317 #6172
Conversation
Beep boop! 🤖 Hey @christophediprima, thanks for your PR! One of my human friends will review this PR and get back to you as soon as possible. Stay awesome! 😎 |
Deploy preview for hasura-docs ready! Built with commit 327abfc |
This is my first pull request. It is not fully completed yet. Any comment or help to complete it is welcome :) |
@christophediprima You can indicate that the PR is not yet ready for review by putting it in a "draft" state. You can do it before you open it, or, for this PR which is already open, click "Convert to draft" on the right-hand side under the "Reviewers" section. |
ee1c66c
to
d1f0ec8
Compare
ea37fd2
to
6e3b6cc
Compare
@abooij I think I am done with the code. Could you help me with the PR remaining checks? I am not sure if they are yes or no. |
@abooij how long do you think it could take to be integrated into a new version? |
Hey @christophediprima! Sorry, I missed your message from last week. Thanks for reminding me, I'll have a look at this PR on Monday. |
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 for this PR, @christophediprima. The Haskell code has been developed very nicely, following the pattern of the other operators accurately. I have no substantial comments on the code itself. Please add one comment for future reference (since this work is overlapping some other work that's currently taking place, and needs to be coordinated somewhat). And I've attempted to improve some test descriptions somewhat.
@beerose, who could review the console part of this PR?
@marionschleifer, could you review the docs for this?
@tirumaraiselvan, could you please review the changelog?
server/tests-py/queries/graphql_query/boolexp/search/select_city_where_not_posix_ci.yaml
Outdated
Show resolved
Hide resolved
server/tests-py/queries/graphql_query/boolexp/search/select_city_where_not_posix_cs.yaml
Outdated
Show resolved
Hide resolved
server/tests-py/queries/v1/select/boolexp/search/select_city_where_not_posix_ci.yaml
Outdated
Show resolved
Hide resolved
server/tests-py/queries/v1/select/boolexp/search/select_city_where_not_posix_cs.yaml
Outdated
Show resolved
Hide resolved
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 for the PR!
Approving console changes.
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.
Docs 👍
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 for the wonderful PR but I think we should use regex
as the base operator name and also use the existing conventions for "not" and "case insensitivity" for the derived operators: https://github.com/hasura/graphql-engine/pull/6172/files#r530185924
As a rule of thumb, during the review phase of a PR, it's not necessary to resolve every conflict, especially e.g. in the changelog. If there are any substantial conflicts, e.g. another PR has been merged that touches a lot of the same code, then it would be wise to resolve the conflict even before your PR is accepted, so that your PR doesn't go out of date too much. When you do resolve conflicts, in this repository we prefer that you do so using merge commits rather than rebases and force-pushes, since:
|
simplify changelog remove cli-ext script fix
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.
@christophediprima Thank you. Just the final minor thing: can you revert the changes to cli-ext/package.json
and cli-ext/tests/sdl/payload.js
files so they are out of this changeset. I think it's just a lint change.
@tirumaraiselvan |
@tirumaraiselvan do I still have to do something or is everything ok? :) |
@christophediprima Congrats, all lights are green! We'll take this up and let you know if there's anything else you can do. |
Thanks for your contribution! Your changes have been merged successfully. |
@christophediprima: @hasura-bot seems to have been confused momentarily about your PR, but rest assured it was merged successfully! |
Description
Add support for following Postgres operators:
Changelog
CHANGELOG.md
is updated with user-facing content relevant to this PR.Affected components
Related Issues
#4317
Solution and Design
Steps to test and verify
Limitations, known bugs & workarounds
Server checklist
Catalog upgrade
Does this PR change Hasura Catalog version?
Metadata
Does this PR add a new Metadata feature?
GraphQL
String_comparison_exp
Breaking changes