fix: use default disk.columns when only other disk.* configs exist #1776
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
de5de558
fix: use default disk.columns when only other disk.* configs existI configured
[disk.name_filter]
and after upgrading to v0.11.0, thedisk widget became empty since
disk.columns
was parsed as an emptyvector unless I added
disk.columns
to my config as well.Issue
N/A
Testing
If relevant, please state how this was tested. All changes must be tested to work:
Using a config like:
v0.11.0 renders an empty disk widget. This PR uses the default disk
widget columns.
If this is a code change, please also indicate which platforms were tested:
Checklist
If relevant, ensure the following have been met:
cargo fmt
)README.md
, help menu, doc pages, etc.)