redhat-developer / redhat-developer/vscode-yaml
Schema validation breaks when using artifactName alias property on PublishPipelineArtifact@1 task
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 829
- Forks
- 260
- Avg merge
- 5h 43m
- Merged PRs (30d)
- 1
Description
Example : PublishPipelineArtifact@1 has a property named artifact with an alias of artifactName
https://github.com/microsoft/azure-pipelines-vscode/blob/main/service-schema.json#L20009
If you make a yml with this content :
steps:
- task: PublishPipelineArtifact@1
displayName: Demo
inputs:
artifactName: MyArtifact
then you get this error
DownloadPipelineArtifact is deprecated - Download a named artifact from a pipeline to a local path
So for some reason it seems to think that this is the DownloadPipelineArtifact task, although that may be a side effect of something else breaking
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the validation error with the YAML example, then inspect service-schema.json around line 20009 and the handling of PublishPipelineArtifact@1 aliases. Trace why artifactName is interpreted as DownloadPipelineArtifact, and verify that the example validates without the deprecation error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100