[ENTRIES] Implements hide_undetected option to mask missing values#166
Merged
HorlogeSkynet merged 1 commit intomasterfrom Mar 2, 2025
Merged
[ENTRIES] Implements hide_undetected option to mask missing values#166HorlogeSkynet merged 1 commit intomasterfrom
hide_undetected option to mask missing values#166HorlogeSkynet merged 1 commit intomasterfrom
Conversation
ingrinder
approved these changes
Mar 1, 2025
Collaborator
ingrinder
left a comment
There was a problem hiding this comment.
Sounds like a good idea, and LGTM!
(partially breaking from an API point of view as
__bool__magic methodEntrydefinition cause objects to behave differently in boolean contexts/operations)
This seems like the more "correct" behaviour anyway 👍
aecb1de to
20bf632
Compare
Owner
Author
|
Changelog and |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
This patch adds a new configuration option to allow hiding "undetected entries".
Reason and / or context
This was wandering in my head for a while now. I guess minimal systems users (with a lot of empty values) may love this option (as this would allow them not to manually adapt
entriesobject to remove unnecessary items).How has this been tested ?
Unit tests + locally.
Types of changes :
(partially breaking from an API point of view as
__bool__magic methodEntrydefinition cause objects to behave differently in boolean contexts/operations)Checklist :