-
Notifications
You must be signed in to change notification settings - Fork 160
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
Feat general improvements #874
Feat general improvements #874
Conversation
if (err !== null) { | ||
console.log('\n'); | ||
error('Opening in default browser. ' + err) |
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.
what exactly are we doing here?why are we saying opening in default browser and appending the error?
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.
When the browser failed to open the link for any reason the error
function will preint
Error: Opening in default browser. ERROR MESSAGE
@@ -269,6 +269,7 @@ const init = new Command("init") | |||
.option("--organizationId <organizationId>", "{{ spec.title|caseUcfirst }} organization ID") | |||
.option("--projectId <projectId>", "{{ spec.title|caseUcfirst }} project ID") | |||
.option("--projectName <projectName>", "{{ spec.title|caseUcfirst }} project ID") | |||
.option(`-sh, --self-hosted`, `Flag for enabling custom endpoint for self hosted instances for non-logged in users`) |
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.
what are we trying to achieve here?
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.
In case the user is not logged in, the project init will prompt the user to login,
By default, all logins are targeted at the cloud, this will give the user the option to add an endpoint
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.
No lets not do this.. There is already a dedicated command for setting endpoint with appwrite client.
We should make sure every command has one job and one job only
Feat collection push improvements
What does this PR do?
--verbose
or--report
--console --open
didn't workwhoami
Check cannot destrucutre selfHosted of undefined
bug