Define schemas in a separate package

[rrousselGit]

Hello!

For the sake of sharing code between backend and frontend, I'd like to define my schema files outside of the package that uses ferry_generator.

Would it be possible to support in the build.yaml a schema that comes from a different package?

[knaeckeKami]

Hi!

Just for clarification:

You want to be able to do something like

• have a separate package that contains the graphql schema
• a separate fronted and backend package, which both depend on the schema package, but contain their own graphql operations

Is this correct?

I'll look into supporting this, should be quite easy, unless there is an unexpected issue with built_value serialization

[rrousselGit]

That is correct, yes.

[knaeckeKami]

a draft PR is available at #606.

still needs a cleanup and tests, but you can already try it out by using

ferry_generator:
   git:
     url: https://github.com/gql-dart/ferry.git
     path: packages/ferry_generator
     ref: external_schema_import 

replace the reference to the schema in build.yaml from

          schema: <current_package>|lib/schema/schema.graphql

to

          schema: <external_dep_packaage>|lib/schema/schema.graphql

[knaeckeKami]

this was released in ferry_generator 0.12.0