-
-
Notifications
You must be signed in to change notification settings - Fork 301
docs: removing customization file contradiction #471
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
Conversation
Customising via the configuration file is clearly possible when using yaml files since you show an example for this. This PR updates the doc to remove the warning that states this is not possible. Given that yaml was the only missing file type in the original warning it seems safe to remove it completely.
Codecov Report
@@ Coverage Diff @@ ## master #471 +/- ## ======================================= Coverage 98.04% 98.04% ======================================= Files 39 39 Lines 1431 1431 ======================================= Hits 1403 1403 Misses 28 28
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report at Codecov.
|
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.
Thanks for fixing the doc!
Description
Customising via the configuration file is clearly possible when using yaml files since you show an example for this. This PR updates the doc to remove the warning that states this is not possible. Given that yaml was the only missing file type in the original warning it seems safe to remove it completely.
Checklist
./script/formatand./script/testlocally to ensure this change passes linter check and testExpected behavior
N/A - Docs updated only
Steps to Test This Pull Request
N/A - Docs updated only
Additional context
N/A - Docs updated only