-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
🐛 Bug Report: Cancelling Initial Migration Creates a Pseudo Project #7685
Comments
Thanks for filing this issue @ItzNotABug! Can you provide specific details on the recreation steps here? Include the relevant URLs/screenshots so we can reproduce. Thanks! |
Hey @EVDOG4LIFE, |
@ItzNotABug Detailed instructions for reproduction can help community members who are new or unfamiliar get to right spot if they wish to contribute. The aim is to create something that anyone with an account can follow and reproduce. For reference, if you're talking about Importing data (eg: https://cloud.appwrite.io/console/project-projectId/settings/migrations) from another platform then it would look roughly like this:
|
Hey @EVDOG4LIFE, I'll also add the requested issue video by later today. Thanks! |
👟 Reproduction steps
Create Project
ButtonImport Project (Experimental)
Imported Project {DateFormat}
is createdThis isn't correct as the project is created before Importing takes place, so the user doesn't have an option to use a Custom ID or a Project Name.
Note: The
console
repository includes this particular dropdown in the source, the Cloud seems to have now removed this particular dropdown. I'll still keep this issue open though.See -
PseudoProject.mov
👍 Expected behavior
Don't create a project if migration is cancelled.
👎 Actual Behavior
Project is created with random ID and Name despite cancelling migration.
🎲 Appwrite version
Appwrite Cloud
💻 Operating system
Linux
🧱 Your Environment
Localhost & Cloud.
👀 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: