🐛 fix +listType marker not working on type alias fields#1359
🐛 fix +listType marker not working on type alias fields#1359sivchari wants to merge 1 commit intokubernetes-sigs:mainfrom
Conversation
k8s-ci-robot
added
do-not-merge/invalid-commit-message
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: sivchari The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
k8s-ci-robot
added
the
size/M
sivchari
force-pushed
the
fix-issue-988-listtype-type-alias
branch
from
06bfcda to
a39b281
Compare
k8s-ci-robot
removed
the
needs-rebase
Include underlying type info (array/object) in schema for slice/map type aliases, allowing field-level markers like +listType to work. Fixes kubernetes-sigs#988 Signed-off-by: sivchari <shibuuuu5@gmail.com>
sivchari
force-pushed
the
fix-issue-988-listtype-type-alias
branch
from
a39b281 to
639035d
Compare
|
Keywords which can automatically close issues and hashtag(#) mentions are not allowed in commit messages. The list of commits with invalid commit messages:
DetailsInstructions 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-sigs/prow repository. I understand the commands that are listed here. |
2 participants
Include underlying type info (array/object) in schema for slice/map type aliases, allowing field-level markers like +listType to work.
Fixes #988