Skip to content

don't ignore config values that fail to parse #19628

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

Merged
merged 1 commit into from
Apr 19, 2025

Conversation

jyn514
Copy link
Member

@jyn514 jyn514 commented Apr 19, 2025

previously, these would just silently be ignored. now they give a warning such as:

invalid config values: /completion/snippets/custom: invalid type: null, expected a map; /cargo/extraEnv: invalid type: null, expected a string;

this also adds a semicolon between errors; previously it was hard to spot that this was actually two different warnings.

cc #19626

previously, these would just silently be ignored. now they give a
warning such as:
```
invalid config values: /completion/snippets/custom: invalid type: null, expected a map; /cargo/extraEnv: invalid type: null, expected a string;
```
@rustbot rustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Apr 19, 2025
Copy link
Member

@Veykril Veykril left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@Veykril Veykril enabled auto-merge April 19, 2025 14:19
@Veykril Veykril added this pull request to the merge queue Apr 19, 2025
Merged via the queue into rust-lang:master with commit 6568e8f Apr 19, 2025
14 checks passed
@jyn514 jyn514 deleted the warn-bad-config branch April 19, 2025 16:29
@ChayimFriedman2
Copy link
Contributor

That probably caused #19641

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-review Status: Awaiting review from the assignee but also interested parties.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants