-
Notifications
You must be signed in to change notification settings - Fork 7
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
Unable to select aliases when importing deps project #2285
Comments
One minimal reproducer:
(Other variants: use If the If the
|
A workaround for the "Manifest type not detected" error is explicitly note the manifest type in your |
The approach that I've taken for this differs from what I expected to do. I had planned to show the available aliases during import and allow them to be selected, but this doesn't work with the quick project import which doesn't show a UI. So what I have done is to allow the invalid project to be imported, but ensure that the project's aliases are shown in the deps tool window even if the project resolution fails, which means the alias can be selected and the project refreshed to fix the problem. |
Fix released in 1.13.1-eap1 on 2023-07-24. |
Fix released in 1.13.1 on 2023-12-07. |
When importing a deps project, sometimes it's necessary to select an alias for the project to even resolve correctly. This can happen when using
:override-deps
or:default-deps
. Without the alias applied, the project is essentially invalid and will not resolve. Cursive should probably present the aliases during project import so that the user can select them for the first project resolution.The text was updated successfully, but these errors were encountered: