Proposal: Allow for custom fields to be added by the user to any instance of any object type.
Benefit: This would greatly extend the flexibility of QLH while allowing power users to get ahead of waiting for an "official" implementation of different features, potentially driving down feature requests as well.
Alternatives: Right now, the only way to do this in QLH is by adding notes in the "Additional information" or "Notes & description" boxes.
Reference implementation: This type of system can be found in password managers, as an example, where the user can create "custom fields" (see this example from Bitwarden).
Examples:
- To give a concrete example, I'd like to add to instances of my contact objects an Apple Verification Code and a GPG public key. While they may not be important for many people (and thus, not likely to be implemented by Quicken), they're important to me.
- Another example is an OTP key URI to back up my TOTPs (i.e., otpauth://TYPE/LABEL?PARAMETERS) in instances of my passwords objects. Alternatively (or additionally), 2FA backup codes could be stored with the login item.
