feat(next): interface prefix for generated types #10691
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ivoilic
changed the title
ivoilic
changed the title
ivoilic
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What?
This adds the option to set an interface prefix in the typescript section of the config. This prefix is then added to the start of all interfaces in the generated types.
Why?
Users may want to use the generated types themselves and prefixing them allows them to be distinct from other types in their app. (Ex: Users vs PayloadUsers or CMSUsers)
How?
This PR adds the new optional property to the config and then uses it inside of
entityToJSONSchemawhere it is appended to the front of the generated interface name. Please note that this update does not append the prefix to manually defined interface names provided in the schema for greater flexibility.