You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #1, we'll implement a way of retrieving a single field from a single entry.
It would be convenient to not be forced to specify which field we want to retrieve all the time.
In most cases, most entries will have a "default field" that we want to copy (e.g. password or token).
We should let the user specify which field they want to be the default field (in coffer create, via CLI options, via the "editor mode", or via the web API).
Questions to be addressed:
What happens when the default field is deleted?
How would the user change which field is the default field for a given entry?
The text was updated successfully, but these errors were encountered:
We have master-field in entries, that seems to be related with default fields, but I don't understand how it currently works. When I view an entry without specifying the field coffer just shows me the entire entry. Moreover, I assume that the master-field is always set to Nothing.
We have master-field in entries, that seems to be related with default fields
That's correct.
Moreover, I assume that the master-field is always set to Nothing.
Yup, for the time being.
When I view an entry without specifying the field coffer just shows me the entire entry
That's a good point. I agree with the current behaviour, coffer /entry should display the whole entry. I'm not sure what the syntax for displaying the default field should be though.
In #1, we'll implement a way of retrieving a single field from a single entry.
It would be convenient to not be forced to specify which field we want to retrieve all the time.
In most cases, most entries will have a "default field" that we want to copy (e.g.
password
ortoken
).We should let the user specify which field they want to be the default field (in
coffer create
, via CLI options, via the "editor mode", or via the web API).Questions to be addressed:
The text was updated successfully, but these errors were encountered: