Prefer non-prelude paths when suggesting import

[Victor-N-Suadicani]

As an example, Bevy's App struct can be found at both bevy::prelude::App and bevy::app::App. I feel that if I am importing App specifically (i.e. not using a glob import on Bevy's prelude), then I would rather use bevy::app::App. Yet rust-analyzer seems to only show me the bevy::prelude::App path. I'd like it to prefer showing me the bevy::app::App path (ideally it would list both, but the non-prelude path first).

[ju1ius]

As a side note there's a rust-analyzer.imports.preferPrelude setting, but I can't get it to work at all.

I'm writing a library with an exposed prelude and RA suggests only the prelude imports with no other alternative.

@Veykril Since you implemented the feature, maybe you have an idea?

[Veykril]

In your case, is the prelude defined in the same crate as where you are working in? In that case it's not surprising this is happening. My change only affects imports coming from other crates, your case is not yet implemented.

Hmm, no that should work. Can you elaborate on the specific setup that runs into problems? It should be working if you set rust-analyzer.imports.preferPrelude to false

[ju1ius]

Can you elaborate on the specific setup that runs into problems?

This is a cargo workspace with a few crates:

+ workspace/
├── .vscode/
│   └── settings.json
├── my-lib/
├── my-lib-macros/
├── my-lib-sys/
└── my-lib-tests/

RA version is 0.3.1791

The RA bits of settings.json:

{
  "rust-analyzer.rustfmt.rangeFormatting.enable": true,
  "rust-analyzer.imports.preferNoStd": true,
  "rust-analyzer.imports.preferPrelude": false,
}

Nothing too fancy...

I do use imports from the main library prelude in the integration tests, but I'd rather not reference the prelude from the main library itself.