This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
Releases
@eddeee888/gcg-typescript-resolver-files@0.7.1
Patch Changes
73d9936: Relax presetConfig.typesPluginsConfig.namingConvention enforcement. Warn if used.
In v0.7.0, 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. If namingConvention is used, we warn instead.
Currently, the preset naively uses the schema type spelling/casing as the generated type. Therefore, it's important to have namingConvention option as keep. In the future, we can revisit to make sure generated resolvers have the same namingConvention support as the generated type file.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
Releases
@eddeee888/gcg-typescript-resolver-files@0.7.1
Patch Changes
73d9936: Relax
presetConfig.typesPluginsConfig.namingConvention
enforcement. Warn if used.In v0.7.0, 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.Currently, the preset naively uses the schema type spelling/casing as the generated type. Therefore, it's important to have
namingConvention
option askeep
. In the future, we can revisit to make sure generated resolvers have the samenamingConvention
support as the generated type file.