-
Notifications
You must be signed in to change notification settings - Fork 26
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
🚀 Feature: Give a hint to where you should run init and deploy commands #87
Comments
@gewenyu99, suggestions on the error? |
Hi, if it's not assigned I'd like to work on this issue |
@stnguyen90 how's this? |
@adarshjhaa100, assigned! Thanks for your interest! 🙏🏼 |
@stnguyen90 I have replaced the error message for the But, for the Do let me know if anything needs to be changed here and I'll make them before raising the PR. |
That sounds reasonable. Go ahead and submit the PR. |
@stnguyen90 I'll raise a PR for this in the SDK Generator within a couple of days. |
@stnguyen90 Have made the changes and raised the PR to SDK generator with attached test cases. Do let me know if there's any issue with the PR and I'll promptly fix and reply. |
@stnguyen90 pushed the latest changes to this PR: appwrite/sdk-generator#720 |
🔖 Feature description
appwrite init [subcommand]
andappwrite deploy [subcommand]
need to be executed in a folder that contains anappwrite.json
file so that that file can be used for the init and deploy, but if you run it from a directory that doesn't contain the file, you might get a cryptic error message like:🎤 Pitch
The init and deploy commands should check for an appwrite.json file and if it doesn't exist, provide an error:
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: