-
Notifications
You must be signed in to change notification settings - Fork 150
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
Merge 2.0.0 into master #404
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#205) * Schema generation and Cypher translation for basic relationship property queries using GraphQL cursor connections Somewhat TCK tested, but still requires integration tests * Connection fields now returned for both queries and mutations An array of new TCK tests validating the new filtering code and projections of connections
* Schema generation and Cypher translation for basic relationship property queries using GraphQL cursor connections Somewhat TCK tested, but still requires integration tests * Connection fields now returned for both queries and mutations An array of new TCK tests validating the new filtering code and projections of connections * Union support
* test: add inital for creating rel properties * feat: add inital for creating rel properties * feat: get unions working with nested create * test: fix ogm tests to include nested create changes
* Schema generation and Cypher translation for basic relationship property queries using GraphQL cursor connections Somewhat TCK tested, but still requires integration tests * Connection fields now returned for both queries and mutations An array of new TCK tests validating the new filtering code and projections of connections * Union support * A couple of loose ends for unions - __resolveType and filtering * Merging 2.0.0 branch is for some reason reverting some of my changes, trying to fix * Make breaking schema changes and fix tests * Update relationship properties, validated by TCK tests * Integration tests for update operations
* test: add cases for connecting with rel properties * feat: add logic for connecting with rel properties * fix: change properties set to use the new appointed name * refactor: only add update with when needed * test: update all breaking tests due to changes in rel properties connect * feat: add union connect support * test: union connect support
* test: add composite where without unions and auth Co-authored-by: Darrell Warde <[email protected]> * feat: added union support for composite where Co-authored-by: Darrell Warde <[email protected]> * config: add husky back Co-authored-by: Darrell Warde <[email protected]>
Update version and mark prerelease
* Update neo-push-server to enforce nodemon uses local ts-node install (force rerun cla check) * Fix typos * refactor: add more debug logs for get jwt Co-authored-by: Evan Reed <[email protected]> Co-authored-by: Matt Murphy <[email protected]> Co-authored-by: Daniel Starns <[email protected]>
* Beginning of documentation for relationship properties * Basic migration guide (navigation a little broken) * Continued work on 2.0.0 docs * Fixed headers not working for new pages (page keys cannot begin with a number) * Remove node from where clause of connect * A couple of outstanding documentation tasks * Highlight that req must be passed into context, add lambda edge case * Clarify Point and CartesianPoint usage in docs
…roperties Feature/enum relationship properties
* Missing copyright headers * Point to prerelease documentation for 2.0.0 branch * General housekeeping before release * Update code comment
* Missing copyright headers * Point to prerelease documentation for 2.0.0 branch * General housekeeping before release * Fixed nullability of Query return type * Update code comment * refactor: remove neoSchema from OGM properties (#256) * feat: add cypherParams (#254) * Use upperFirst from graphql-compose in all cases (#262) * Remove upper-case-first and our own util function from @neo4j/graphql - use upperFirst from graphql-compose * Re-export graphql-compose upperFirst from @neo4j/graphql for use in @neo4j/graphql-ogm, remove upper-case-first dependency * Fix TCK tests broken from merge Co-authored-by: Daniel Starns <[email protected]>
Fix broken link
Fix typo, relationship properties type should be interface
…alars Fix the use of custom scalar/enum values as return type for custom Cypher
Documentation changes following editorial comments
* refactor: change schema references from relationship to edge * docs: add note about relationship and edges
Rephrase sentence to be passive
Update relationships.adoc
* feat: throw error when using reserved names * test: error when using reserved names * docs: remove useage of Node type * refactor: changes from PR comments
Bring 2.0.0 in line with master
…onnections-from-custom-cypher Fix multiple connections being returned from custom Cypher
Remove surplus _IN and _NOT_IN filters for relationships
Fix for aliasing connection multiple times
Remove prerelease marker
oskarhane
approved these changes
Aug 10, 2021
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.
🔥
danstarns
approved these changes
Aug 10, 2021
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.
🍻
darrellwarde
added a commit
that referenced
this pull request
Aug 10, 2021
This reverts commit 716f939.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Merges the 2.0.0 branch into master, ready for release! 👀
Issue
#192