Open muni-corn opened 4 years ago
For backwards compatibility, the account
option can still be available, and mvelopes will just try to infer the account type. If it can't, it will let the user know and suggest the new convention as outlined above.
Just had this idea for a new convention for defining accounts:
This simplifies the categorizing of different account types, which mvelopes will need for future features.
This won't change how accounts are added to entries, as they can still be added by their full names (and in fact, by no other way):
If users want to change the name of these top-level accounts, we could add these sorts of options:
This doesn't replace the default top-level names, so these user-defined names can be used in tandem with the default names:
In fact, users could define multiple top-level names if they want: