Disable warning when using non-latest nightly

[trolley813]

Sometimes the latest nightly lacks RLS, so one need to fix the specific nightly build (such as nightly-2019-03-10) in order to use the RLS. But setting "rust-client.channel": "nightly-2019-03-10" in the settings.json gives a warning that the value is not accepted (however it works perfectly, VSCode uses the exact version given).

Suggestion: allow setting rust-client.channel variable to nightly-YYYY-MM-DD template (alongside with stable, beta and nightly).

[Xanewok]

I'm somewhat torn - I'd like for the option to suggest few values from the enum but still allow for manual override; however, I don't believe that's possible using the VSCode settings schema.

[resinten]

Bumping this issue. I encountered this. In fact, until reading this issue, I was under the impression that the extension was not accepting the specific nightly reference due to this warning message. I took out the config because I thought it was failing on that. So then I struggled because I could not get it to use the version of nightly I needed it to use, even though I had changed mine default toolchain through rustup and cargo was using it. It resulted in builds working with cargo and failing according to RLS. I ended up disabling the extension altogether out of frustration. I wish I had known that it was using the desired channel even though the warning was implying it didn't. I agree that this should be changed. Either that or this should be restricted to only allow those options and another config should be exposed for the detailed spec. I would prefer the former.