schema/type any=True breaks schema composition #945
Description
What steps did you take:
File: 1.schema.yaml
#@data/values-schema
---
#@schema/type any=True
something: {}
File: 2.schema.yaml
#@data/values-schema
---
something:
#@overlay/match missing_ok=True
list:
- name: ""
File: values.yaml
#@data/values
---
something:
list:
- name: "one"
- name: "two"
Command:
ytt -f . --data-values-inspect
What happened:
something:
list:
- name: ""
- name: one
- name: two
What did you expect:
something:
list:
- name: one
- name: two
Anything else you would like to add:
For some reason, when using the schema/type any=True annotation, ytt adds an item from the additional schema to the resulting list.
Without this annotation, the result doesn't contain items from the schema, as expected.
File: 1.schema.yaml
#@data/values-schema
---
something: {}
Environment:
- ytt version (use
ytt --version): ytt version 0.51.1 - OS (e.g. from
/etc/os-release): MacOS 15.3.1
Vote on this request
This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.
👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"
We are also happy to receive and review Pull Requests if you want to help working on this issue.