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

Offer to migrate local context to global context when creation of global context lead to conflict #743

Open
ptitFicus opened this issue Dec 3, 2023 · 0 comments

Comments

@ptitFicus
Copy link
Member

  1. Create a project "foo"
  2. Create a local context / subcontext
  3. Create the same global context / subcontext <- this results in an error explaining the conflict

There is currently no easy way to solve this situation, a nice thing would be a popup offering to migrate the local context in a global one. This would imply to make the change for associated overload an subcontexts.

@ptitFicus ptitFicus transferred this issue from another repository Mar 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant