Follow-up from #1552, starting at #1552 (comment).
The missing auto-resolved namespace alias inspection currently suggests quick fixes for every namespace that has been observed using the requested alias elsewhere. This can produce misleading suggestions when multiple namespaces use the same alias name, but only one of them contains/uses the concrete keyword.
Example from the original report: for ::specs/version, if both app.specs1 and app.specs2 have been required as specs somewhere, Cursive may suggest both, even when only :app.specs1/version exists.
Requested behavior:
- For
::alias/name, only suggest candidate namespaces where the resolved keyword :candidate-ns/name is known to exist in the keyword index.
- Continue to support non-spec namespaced keyword usages, not only spec definitions.
This should reduce false positives while preserving the existing general keyword-alias quick fix behavior.
Follow-up from #1552, starting at #1552 (comment).
The missing auto-resolved namespace alias inspection currently suggests quick fixes for every namespace that has been observed using the requested alias elsewhere. This can produce misleading suggestions when multiple namespaces use the same alias name, but only one of them contains/uses the concrete keyword.
Example from the original report: for
::specs/version, if bothapp.specs1andapp.specs2have been required asspecssomewhere, Cursive may suggest both, even when only:app.specs1/versionexists.Requested behavior:
::alias/name, only suggest candidate namespaces where the resolved keyword:candidate-ns/nameis known to exist in the keyword index.This should reduce false positives while preserving the existing general keyword-alias quick fix behavior.