-
Notifications
You must be signed in to change notification settings - Fork 28
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
add package name sanitisation #212
Conversation
test/nodeshift-config-test.js
Outdated
'openshift-rest-client': () => { return Promise.resolve({}); } | ||
}); | ||
|
||
const tmpDir = require('os').tmpdir() |
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.
Wasn't certain about creating an item in examples/
with an invalid name, so I took this approach instead. Happy to create a file in the repo if preferable.
@evanshortiss i was on PTO last week, so i'll get this today hopefully |
@lholmquist no sweat, it's a minor enough issue anyways! |
lib/nodeshift-config.js
Outdated
@@ -31,11 +31,16 @@ async function setup (options = {}) { | |||
options.nodeshiftDirectory = '.nodeshift'; | |||
options.projectLocation = options.projectLocation || process.cwd(); | |||
|
|||
|
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.
looks like a stray extra line here
other than that 1 comment, i think this should work. maybe just squash those commits into 1 |
Attempting to deploy an application that fails to meet openshift's naming rules will result in misleading error messages being returned. This commit addresses the issue by verifying the package.name is compliant with openshift's naming restrictions. fix linter issues remove wc file remove added line
46dead5
to
9f54b9a
Compare
@lholmquist think we should be good now 👍 |
released as 1.7.1 |
Attempting to deploy an application that fails to meet openshift's
naming rules will result in misleading error messages being returned.
This commit addresses the issue by verifying the package.name is
compliant with openshift's naming restrictions.
See issue #211