Schema override parameter in ppx argument

[arnarthor]

This adds an additional optional parameter to the ppx usage where you can locally override the desired schema to validate the query against.

This is fully backwards compatible with the old API and only extends it to allow for usage such as this

Reason

module MyQuery = [%graphql
  {|
    query pokemon($id: String, $name: String) {
      pokemon(name: $name, id: $id) {
        id
        name
      }
    }
  |};
  "pokedex_schema.json"
];

OCaml

module MyQuery = [%graphql
  {|
    query pokemon($id: String, $name: String) {
      pokemon(name: $name, id: $id) {
        id
        name
      }
    }
  |};;
  "pokedex_schema.json"
];

By adding this extra parameter, the PPX now supports having multiple different GraphQL APIs in a single project without the need for yarn workspaces or similar solutions.

If the parameter is skipped, it falls back to the default schema from the config (graphql_schema.json)

[idkjs]

@arnarthor how are you installing this in your projects?

I'm trying yarn add https://github.com/sothebys/graphql_ppx.git#schema-override-parameter-in-ppx-argument but not getting any luck.

[arnarthor]

@idkjs Yeah because it needs built artifacts you can't install it directly from this git repo (it has some pre publish builds on npm).

Use this commit https://github.com/sothebys/graphql_ppx.git#7f5b43ae0e79ee80474110f104fba1a3ac371be1

You can see it here (https://github.com/sothebys/graphql_ppx/commits/merged-remote) where we've pushed the built artifacts to git.

[idkjs]

Thank you, sir.
Second link is a dead link. Does that mean its been pushed or is the link wrong?

[idkjs]

@arnarthor any plans to move this to bsplatform 6.2.1?

[arnarthor]

Yes, we have it on our roadmap at work to upgrade to 6.x in desember

[arnarthor]

This implementation has been moved to the maintained graphql_ppx here