Add path to global.json in SDK resolution error message when it's available #25823
Labels
Area-CLI
cli-ux
Issues and PRs that deal with the UX of the CLI (exit codes, log output, verbs/options, and so on)
good first issue
Issues that would be a good fit for someone new to the repository. Narrow in scope, well-defined.
Milestone
SDK resolution error messages currently look like this:
This is helpful, but doesn't tell the user which global.json is impacting the resolution. This is often fairly straightforward to find out (since global.json is heirarchical, it must be at or above the working directory of the process invocation), but can be outside of what the user expects.
We should incorporate the path to the global.json into this message when it is available for every message that mentions global.json, for the following named message strings (as possible) (list valid as of this commit):
Here are the docs for the native API:
Per these docs, if we have a 'requested version' in our result, then a global.json was present, so we should always have the path. Therefore it should be safe to have two variants of most of these messages:
Originally posted by @baronfel in #25733 (comment)
This is related to #24480
The text was updated successfully, but these errors were encountered: