-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Schema wants OTP to be a string, but it's really a number #351
Comments
I'm not entirely familiar with the OTP parameter. Is the OTP parameter always a number? As a workaround, I'll suggest doing the following: - nx run utilities:deploy-npm --otp=634119
+ nx run utilities:deploy-npm --otp='634119' |
If the right path is changing the OTP type to a number, not a string, we are open to receiving the contribution. A good starting point is changing the type of the OTP parameter on: |
Not entirely sure, but it seems like it is. Still, For now I think the proper workaround would be accepting both
This unfortunately makes no difference, it still gets converted to a number by Nx. :( |
I was able to make it run with: - nx run utilities:deploy-npm --otp=634119
+ npx nx deploy node-lib1 --otp "'634119'" But I still think it can be improved by changing the type |
Providing the OTP by passing it through the CLI fails as the value provided is coerced into a number, rather than staying a string like the executor schema expects.
As a workaround, I've patched the schema to expect a number and it works just fine.
Using Nx 14.3.6 and ngx-deploy-npm 4.1.2.
The text was updated successfully, but these errors were encountered: