fix: use gen.yaml structure for config metadata #4
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
SPE-1295 Make rest of gen.yaml config options and workflow file options "data-driven"
Currently, the language-specific fields for SDK config in the UI are pulled directly from the openapi generation (such as here). The purpose of that is to keep the config options in the UI always up to date with what is expected by the generator However, there are still many configuration options in gen.yaml and the action that are not configurable via the UI. Some noteable examples include SdkClassName (gen.yaml) and PR mode (workflow file). We should resolve that by making those configs "data driven" in the same way the language config fields are |
anuraagnalluri
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.
No description provided.