-
Notifications
You must be signed in to change notification settings - Fork 74
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
cli: use async await insted of then in deploy #2885
cli: use async await insted of then in deploy #2885
Conversation
c5f1881
to
a29425a
Compare
a29425a
to
9a234c5
Compare
const choices = [ | ||
'No, I need to create a new one (Signup)', | ||
'Yes, I do. (Login)', | ||
] | ||
return prompt([ | ||
const inp = await prompt([ |
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.
const userInput
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.
const {signupConfirmation} = await ...
else return this.askSignup() | ||
}) | ||
]) | ||
if (inp.signupConfirmation == choices[1]) return this.askLogin() |
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.
===
## Description Use new endpoints /v2/bots/ to deploy. Send the bot_config as parameters in the POST call /v2/bots/ instead of adding the json in the separate folder next to the bot zip of the bot to be deployed.
5e64f32
into
BLT-1008-create-json-with-config-file-on-botonic-deploy
Description
Refactor the deploy file to always use async await instead of chaining asyncorn functions with callbacks inside the then function.
Context
Approach taken / Explain the design
To document / Usage example
Testing
The pull request...