Skip to content

Use schema-ast plugin#307

Merged
eddeee888 merged 10 commits into
master-nextfrom
generate-schema-ast
Jun 30, 2024
Merged

Use schema-ast plugin#307
eddeee888 merged 10 commits into
master-nextfrom
generate-schema-ast

Conversation

@eddeee888
Copy link
Copy Markdown
Owner

No description provided.

@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Jun 27, 2024

⚠️ No Changeset found

Latest commit: fcad6e0

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

}

if (mergeSchema === true) {
return { path: 'schema.generated.graphql', config: {} };
Copy link
Copy Markdown
Owner Author

@eddeee888 eddeee888 Jun 27, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The default schema.generated.graphql can be picked up by the majority of schema setup.

**/*.graphql is a common pattern which will pick up both the generated version and the unmerged version 🤔

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changed the default to schema.generated.gql to avoid this issue

@eddeee888 eddeee888 mentioned this pull request Jun 30, 2024
@eddeee888 eddeee888 force-pushed the generate-schema-ast branch from e2f52af to b84ad7f Compare June 30, 2024 06:30
@eddeee888 eddeee888 merged commit d7fdaa2 into master-next Jun 30, 2024
@eddeee888 eddeee888 deleted the generate-schema-ast branch June 30, 2024 06:42
eddeee888 added a commit that referenced this pull request Jun 30, 2024
* Handle Enum resolvers (#293)

* Add logic to handle Enum types: wireup, mapper, resolverGeneration

* Add e2e test for Enum mappers in auto-wireup test

* Fix the need to alwasy having to add enum mapper when generating enum resolver files

* Rebase tests to have default enum values

* Add changeset

* Fix unit tests

* Ensure enums with mapper types are always generated to avoid runtime issues

* Set up test for enum with mappers must have file generation

* Update test snapshot

* Ensure all allowed enums are generated to avoid runtime error (#296)

* Add functionality to ensure all allowed fields are generated

* Add changeset

* Fix unit test

* Update changeset

* Fix validatePresetConfig tests

* Use typescript resolvers meta to support `namingConvention` for generated types of GraphQL definitions (#301)

* Use meta from generated types for resolver type names

* Update e2e tests

* Add changeset

* Fix lint/unit test

* Update e2e tests for namingConvention to capture all possible types

* Add FIXME to update meta

* Fix lint

* Fix typo (#303)

* Fix typo

* Update baseline tests

* Use meta for accurate resolvers map type (#304)

* Temporarily use alpha version to test

* Use resolversType from meta

* Baseline test with typesPrefix for more coverage

* Add changeset

* Bump to latest version

* Use schema-ast plugin (#307)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant