Closed eddeee888 closed 1 year ago
Latest commit: d2d083fd45d52d753c69d1c7f39f7ba8af3cf8c6
The changes in this PR will be included in the next version bump.
Not sure what this means? Click here to learn what changesets are.
Click here if you're a maintainer who wants to add another changeset to this PR
/release-snapshot
✅ Successfully published package/s with tag pr188-run314-1
!
Currently, the preset is naively uses the schema type as the generated type. Therefore, it's important to have
namingConvention
option askeep
.Previously, we've made
presetConfig.typesPluginsConfig.namingConvention
to throw if used. In this release, we've relaxed it because certain options may still work e.g.upperCaseFirst
. IfnamingConvention
is used, we warn instead.In the future, we can revisit to make sure generated resolvers have the same
namingConvention
support as the generated type file.