Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update YAML editor to provide default content #2636

Merged
merged 1 commit into from
Dec 12, 2022

Conversation

AlanGreene
Copy link
Member

@AlanGreene AlanGreene commented Dec 12, 2022

Changes

Related to #2437

If the user switches to YAML mode in the Create PipelineRun page we should not present them with an empty editor. At the very least we should prepopulate it with the basic outline of a PipelineRun, i.e. apiVersion, kind, metadata with default name + namespace placeholder, spec.

If the user has already updated the form before switching to YAML mode, preserve their selected inputs and display the corresponding YAML so they can continue editing as needed.

Remove unused code from the YAML editor related to loading of the Pipeline resource.

For example, the following form:
image

generated this YAML:
image

/kind feature

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

  • Docs included if any changes are user facing
  • Tests included if any functionality added or changed
  • Follows the commit message standard
  • Meets the Tekton contributor standards (including
    functionality, content, code)
  • Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
  • Release notes block below has been updated with any user facing changes (new features, significant UI changes, API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
  • Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

When switching to YAML mode on the Create PipelineRun page, pre-populate the editor with either a basic PipelineRun outline, or YAML corresponding to the selected inputs on the form.

@tekton-robot tekton-robot added kind/feature Categorizes issue or PR as related to a new feature. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Dec 12, 2022
If the user switches to YAML mode in the Create PipelineRun page we
should not present them with an empty editor. At the very least we
should pre-populate it with the basic outline of a PipelineRun, i.e.
`apiVersion`, `kind`, `metadata` with default name + namespace
placeholder, `spec`.

If the user has already updated the form before switching to YAML
mode, preserve their selected inputs and display the corresponding
YAML so they can continue editing as needed.

Remove unused code from the YAML editor related to loading of the
Pipeline resource.
@AlanGreene AlanGreene force-pushed the create_yaml_forminputs branch from 78c13bf to 2df075d Compare December 12, 2022 15:52
Copy link
Contributor

@briangleeson briangleeson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Dec 12, 2022
@tekton-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: briangleeson

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 12, 2022
@tekton-robot tekton-robot merged commit e58b8cd into tektoncd:main Dec 12, 2022
@AlanGreene AlanGreene deleted the create_yaml_forminputs branch December 12, 2022 17:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/feature Categorizes issue or PR as related to a new feature. lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants