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
Currently, the tree-sitter grammar recognizes all key-value lines within a transaction as children of that transaction node. This behaviour is in line with the beancount grammar and parser behaviour. However, it necessitates a post-processing step to match key-value lines to postings or the transaction itself.
With some light trickery in the grammar/scanner, it should be possible to match key-value lines to postings during parsing. However, this would cause some deviation of the grammar from beancount's.
Would this be an acceptable change in your opinion?
The text was updated successfully, but these errors were encountered:
Currently, the tree-sitter grammar recognizes all key-value lines within a transaction as children of that transaction node. This behaviour is in line with the
beancount
grammar and parser behaviour. However, it necessitates a post-processing step to match key-value lines to postings or the transaction itself.With some light trickery in the grammar/scanner, it should be possible to match key-value lines to postings during parsing. However, this would cause some deviation of the grammar from
beancount
's.Would this be an acceptable change in your opinion?
The text was updated successfully, but these errors were encountered: