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

Fix to FieldError fields name for duplicate param names #2195

Merged
merged 1 commit into from
Mar 9, 2020
Merged

Fix to FieldError fields name for duplicate param names #2195

merged 1 commit into from
Mar 9, 2020

Conversation

skaegi
Copy link
Contributor

@skaegi skaegi commented Mar 9, 2020

Fixes #2192

Changes

Changes field name from spec.inputs.params to spec.params.name to be consistent with other validation checks.

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

See the contribution guide for more details.

Double check this list of stuff that's easy to miss:

Reviewer Notes

If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.

@googlebot googlebot added the cla: yes Trying to make the CLA bot happy with ppl from different companies work on one commit label Mar 9, 2020
@tekton-robot tekton-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Mar 9, 2020
@vdemeester vdemeester added this to the Pipelines 0.11 🐱 milestone Mar 9, 2020
@vdemeester vdemeester added the needs-cherry-pick Indicates a PR needs to be cherry-pick to a release branch label Mar 9, 2020
Copy link
Member

@vdemeester vdemeester left a comment

Choose a reason for hiding this comment

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

/meow
/lgtm

/cc @sbwsg

@tekton-robot tekton-robot requested a review from a user March 9, 2020 18:06
@tekton-robot
Copy link
Collaborator

@vdemeester: cat image

In response to this:

/meow
/lgtm

/cc @sbwsg

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@tekton-robot tekton-robot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Mar 9, 2020
@dibyom
Copy link
Member

dibyom commented Mar 9, 2020

I think the unit test needs to be fixed as well!

@skaegi
Copy link
Contributor Author

skaegi commented Mar 9, 2020

so embarrassed .... yes

@vdemeester
Copy link
Member

Oopps, I got too confident, too quickly 😹

@tekton-robot tekton-robot removed the lgtm Indicates that a PR is ready to be merged. label Mar 9, 2020
Copy link
Member

@dibyom dibyom left a comment

Choose a reason for hiding this comment

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

Nit: Would you mind squashing up the commits @skaegi ? Otherwise, LGTM!

@tekton-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dibyom, sbwsg, vdemeester

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:
  • OWNERS [dibyom,sbwsg,vdemeester]

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

…d unit test

Changes field name from spec.inputs.params to spec.params.name to be consistent with other validation checks.
Fixes #2192
@dibyom
Copy link
Member

dibyom commented Mar 9, 2020

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Mar 9, 2020
@tekton-robot tekton-robot merged commit 2606f74 into tektoncd:master Mar 9, 2020
@ghost ghost removed the needs-cherry-pick Indicates a PR needs to be cherry-pick to a release branch label Mar 9, 2020
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. cla: yes Trying to make the CLA bot happy with ppl from different companies work on one commit lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

TaskRun validation with duplicate params is incorrect
5 participants