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
Typed metadata are handled like regular metadata (and hence always rendered as string literals) when used on commodities (at least), whereas they work properly on transactions.
The problem is that we use pp_metadata to print this (line 2625) which doesn't handle typed metadata where for transactions we create a metadata object using create_metadata_from_regex (line 1143) and that is printed correctly.
I need to check how to harmonize/unify this.
I'm away for 10 days starting on Saturday, so this will have to wait until February.
Typed metadata are handled like regular metadata (and hence always rendered as string literals) when used on commodities (at least), whereas they work properly on transactions.
For example, the following ledger snippet:
is translated by ledger2beancount to the following beancount snippet:
Note the (incorrect) double quotes around
typed_metadata
value in theEUR
commodity, which are (correctly) missing in the transaction case.The text was updated successfully, but these errors were encountered: