Skip to content
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

Minor Bug: After switching the server it might be impossible to create a new plan #134

Open
appreciated opened this issue May 24, 2024 · 3 comments
Assignees

Comments

@appreciated
Copy link
Contributor

appreciated commented May 24, 2024

Precondition

  1. User logs into a server ( pdx sign-in)
  2. User creates a plan in directory "a" ( pdx new)
  3. User switches to another server ( pdx sign-in)
  4. User tries to create a plan in the same directory ( pdx new)

Current behaviour

appreciated@DESKTOP:~$ pdx new
🚨 Error creating plan
  → Project does not exist in org

Expected behaviour

A more helpful message and an action that allows to resolve the issue. At least a message about how to resolve the issue.

appreciated@DESKTOP:~$ pdx new
🚨 Warning: A plan was already created in this directory for another project to which you do not have access to. 
Would you like to create a new project (y/n)?
@danenania
Copy link
Contributor

Thanks for flagging this--I agree this should be smoothed out. The work around for now is to delete the .plandex (or .plandex-dev) directory.

@appreciated
Copy link
Contributor Author

appreciated commented May 24, 2024

@danenania thanks for your swift response!
I thought about this for a bit. Wouldn't it be better for the long shot to allow storing multiple projects in the same .plandex folder and also include the user-id and the server url. This way, it would be clear that the project does not belong to the current user and no error message would be necessary.

@danenania
Copy link
Contributor

@appreciated Yeah, I think you're right that it would be a better approach.

@danenania danenania self-assigned this Nov 9, 2024
danenania added a commit that referenced this issue Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants