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

Lint error when dependency with same is defined multiple times #3068

Merged

Conversation

kichristensen
Copy link
Contributor

What does this change

Creates a lint error when multiple dependencies are specified with the same name.

What issue does it fix

Closes #3067

Notes for the reviewer

The reason the lint code is porter-102 is because of #3034 which uses porter-101

Checklist

  • Did you write tests?
  • Did you write documentation?
  • Did you change porter.yaml or a storage document record? Update the corresponding schema file.
  • If this is your first pull request, please add your name to the bottom of our Contributors list. Thank you for making Porter better! 🙇‍♀️

Having multiple dependencies with the same name results in undefined
behaviour. This change introduces a lint to ensure that no dependencies
share the same name.

Signed-off-by: Kim Christensen <kimworking@gmail.com>
Signed-off-by: Kim Christensen <kimworking@gmail.com>
@kichristensen kichristensen changed the title Lint dependency multiple times Lint error when dependency with same is defined multiple times Apr 7, 2024
Signed-off-by: Kim Christensen <kimworking@gmail.com>
@schristoff schristoff merged commit e7fdd77 into getporter:main Apr 8, 2024
15 checks passed
@kichristensen kichristensen deleted the lintDependencyMultipleTimes branch April 9, 2024 22:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Specifying multiple dependencies with the same name doesn't produce an error or warning
2 participants