-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Adding top-level fields to CLI show and clip commands #8241
Conversation
Note that one consequence of the current implementation is that it won't be possible anymore to select an attribute from the CLI if it has the same name as a top-level field. I feel like this is a fair limitation. Also, we might consider removing the braces around the UUID. I'm not even sure why they are there in the first place. |
Codecov Report
@@ Coverage Diff @@
## develop #8241 +/- ##
===========================================
- Coverage 64.45% 64.44% -0.01%
===========================================
Files 339 339
Lines 43732 43749 +17
===========================================
+ Hits 28186 28191 +5
- Misses 15546 15558 +12
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
Need to fix code format then can merge |
@droidmonkey ready to merge, when/if the mac tests ever finish. |
89d562e
to
73a6faa
Compare
The top-level fields are currently not accessible from the CLI, which makes it impossible to select entries or groups based on the UUID. There are other top-level fields I believe, like the expiry date, but I only added the two most critical fields for the moment.
Fixes #4112
Preparation work for #4113 and #3720
The top-level fields are currently not accessible from the CLI, which
makes it impossible to select entries or groups based on the UUID.
There are other top-level fields I believe, like the expiry date, but
I only added the two most critical fields for now. I also considered
defining the constants in
Entry
instead ofEntryAttributes
, becausethey are not attributes per se. I'm not sure which choice is better tbh.
Testing strategy
Updated the unit tests.
Type of change