feat:modify the format of the exported file #4040
Merged
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.
🤖 Generated by Copilot at 3b2b8c2
Summary
📄🐛🆕
This pull request modifies the frontend code of several providers to export a single YAML file instead of a ZIP file when exporting templates or applications. This simplifies the export process and removes the dependency on JSZip. It also adds support for the new template type attribute in the backend and fixes a bug in the cronjob provider.
Walkthrough
getUserServiceAccount
function in theuser.ts
file by returning the user field from the context object instead of the namespace field (link)template_type
field to theTemplateType
type definition in theapp.ts
file and thehandleTemplateToInstanceYaml
function in thejson-yaml.ts
file to support the new template type attribute that was introduced in the backend (link, link, link)defaultInputes
variable and thegenerateCorrectYaml
function in theindex.tsx
file (link)>
character to the previous line in several files to follow the code style convention of the project (link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link)