fix(ts): ensures patches are preserved during code generation #166
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
troian
approved these changes
May 3, 2024
|
🎉 This PR is included in version 1.2.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
This pull request is a cherry-pick of PR #147 from the
akash-apirepository. It aims to enhance the code generation process by ensuring that patches to the generated code are preserved and by adding automated formatting post-generation.Key Changes
Preservation of Patches: This cherry-pick ensures that any patches applied to the generated code are maintained during subsequent code generations. This is crucial for incorporating custom modifications or fixes that are necessary for our operational requirements without having to reapply them manually each time the code is regenerated.
Automated Formatting: Post code generation, this PR introduces an automated formatting step. This step is designed to minimize diff noise in future commits and ensure consistency across the codebase. It helps maintain a cleaner and more readable code structure, making it easier to manage and review.