-
Notifications
You must be signed in to change notification settings - Fork 301
Refactor PostgresJSON Tests #1072
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
Refactor PostgresJSON Tests #1072
Conversation
parsonsmatt
left a comment
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 first pass! I think we can make some further improvements and that'll help.
Co-Authored-By: Matt Parsons <parsonsmatt@gmail.com>
…istent into json-postgres-tests
|
@parsonsmatt I made the changes you request. I ended up just making all the tests work with the same setup, as I was having trouble adding a second |
|
Fantastic, thanks! This is great work 😄 If you'd like, you can add a |
|
awesome thanks! |
|
Thanks for your guidance on this Matt, I really appreciate it. |
I wasn't sure how to put all of the db entry keys into scope. I made some ad hoc data structures to do so, but if anyone has any suggestions on how to do this better I would be open to them!
Before submitting your PR, check that you've:
Bumped the version numberDocumented new APIs with Haddock markupAdded@sincedeclarations to the HaddockAfter submitting your PR:
Update the Changelog.md file with a link to your PR