Graphile Crystal (PostGraphile V5, Grafast, etc) #1747
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
…erty which is the underlying Postgres client for use with `pgTyped`, `zapatos`, and other libraries that can use a raw postgres client. This is exposed via `NodePostgresPgClient` interface which is a subtype of `PgClient`.
Releases: @dataplan/json@0.0.1-beta.4 @dataplan/pg@0.0.1-beta.4 @grafserv/persisted@0.0.0-beta.4 grafast@0.0.1-beta.4 grafserv@0.0.1-beta.4 graphile-build-pg@5.0.0-beta.6 graphile-build@5.0.0-beta.5 graphile-utils@5.0.0-beta.6 graphile@5.0.0-beta.6 pgl@5.0.0-beta.6 postgraphile@5.0.0-beta.6 [skip ci]
`.expression` doesn't exists and I think `.select` is the correct way.
…e equivalent to input values
…alence" feature to enable collapsing of request waterfalls.
|
Does v5 support GET method out of the box, I am asking because a related issue is referenced here? |
|
Please file a separate issue, ask in the relevant issue (e.g. #442), or ask in chat in future. Yes; see: https://postgraphile.org/postgraphile/next/config#grafserv-options |
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.
This "PR" (not really a PR) has been just over 3 years in the making! It merges together the PostGraphile and Graphile Engine repositories into a monorepo, and then replaces the lookahead system in Graphile Engine with a new dedicated execution engine called Grafast. Grafast comes with its own HTTP server compliant with the GraphQL-over-HTTP spec, and this server is built via abstractions that enable it to support a much wider variety of web server frameworks, no longer requiring there to be an underlying Node
httpserver. Since everything has been rebuilt from the ground-up on top of the new Grafast engine, a ridiculously huge amount of code has changed, so I had to roll back themainbranch of this repo to the state it was at PostGraphile v4.7 (3.5 years ago, when the V5 work branched off). For PostGraphile V4, please see thelegacybranch.To read more about what this means, please read:
I think it fixes the following issues, and probably loads more:
createPostGraphileSchemaDocuments the Entire Database #1663NodeIDsupport in custom functions #979@graphile-contrib/defaultspackage #1718selectGraphQLResultFromTable#1659fieldreturningenumfails #1601useAsteriskfromselectGraphQLResultFromTablegraphile-engine#765deletedUserIdis different from useridgraphile-engine#763foo = barinstead of sql.fragmentfoo = bargraphile-engine#730Maps should useStringas key? graphile-engine#603OrderSpectype inmakeAddPgTableOrderByPluginis too restrictive graphile-engine#593