-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
feat(gitlabci): Use schema for dep extraction #33586
base: main
Are you sure you want to change the base?
Conversation
const docs = parseYaml(content, { uniqueKeys: false }); | ||
for (const dep of GitlabDocumentArray.parse(docs)) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pass schema via customSchema
option to parseYaml
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, its type inference doesn't work correctly. In order to fix it, I need first write schemas for all cases that pass generic unchecked type T
to the parseSchema
. Until then, customSchema
is discouraged.
TLDR; if I do, the type of docs
will be unknown[]
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ups, conflicted 🙃 |
# Conflicts: # lib/modules/manager/gitlabci/extract.spec.ts
Changes
Context
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: