-
Notifications
You must be signed in to change notification settings - Fork 221
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
Add validation to esp-config
#2475
Conversation
94f0812
to
4580560
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM and I think this is enough - not even sure we'll ever really use Custom
(but maybe we will)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, I'm confused by one thing but that may just be me. Thanks!
.join(format!("{prefix}config_table.md")) | ||
.to_string_lossy() | ||
.join(format!("{prefix}_config_table.md")) | ||
.display() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think I understand why we convert a PathBuf into a string before we pass it to something that needs an AsRef.
Opening as a draft, as this will need rebasing and additional changes once #2422 and #2246 get merged.
I have not actually taken advantage of the validation in any of the packages depending on
esp-config
, not sure if that should be considered in-scope for this or be handled in a subsequent PR. Will take some time to do this.skip-changelog
added as theesp-config
package does not have aCHANGELOG.md
, and there are no user-facing changes here.Closes #2206