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

fix(config): Allow scoped applications in the package name. #539

Merged
merged 2 commits into from
Feb 12, 2021

Conversation

lholmquist
Copy link
Member

  • This modifies the logic that was used to determine if an applications package name was valid. Previously, nodeshift would error when using scoped packages. Since @org/pkg is valid in npm, this is now valid with nodeshift. scoped package names will be updated to org-pkg for the Openshift Objects the CLI creates.

fixes #538

* This modifies the logic that was used to determine if an applications package name was valid.  Previously, nodeshift would error when using scoped packages.  Since @org/pkg is valid in npm,  this is now valid with nodeshift.  scoped package names will be updated to org-pkg for the Openshift Objects the CLI creates.

fixes nodeshift#538
@lholmquist lholmquist requested a review from a team February 11, 2021 18:59
@coveralls
Copy link

coveralls commented Feb 11, 2021

Coverage Status

Coverage increased (+0.001%) to 98.643% when pulling f645704 on lholmquist:538-scope-package-validation into 4206d3b on nodeshift:master.

@lholmquist lholmquist marked this pull request as draft February 11, 2021 18:59
@lholmquist lholmquist marked this pull request as ready for review February 11, 2021 19:04
@lholmquist lholmquist merged commit 0e4a5db into nodeshift:master Feb 12, 2021
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.

Can't deploy @org packages
2 participants