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
Some invoice attributes, like buyer and seller would benefit from a nested structures. Like seller->country. I suggest to user a dot as separator to add "fake" nesting. I didn't find a good way to nest it natively without too many changes.
Example: factx['seller.country']
Steps to implement:
Find xpaths for missing nested attributes and add to fields.yml
Any changes needed to use nested attributes.
The text was updated successfully, but these errors were encountered:
We could simply call our nested fields seller_name, seller_country, etc. So use the underscore directly instead of the dot. This would save the trouble of replacing it.
Some invoice attributes, like buyer and seller would benefit from a nested structures. Like
seller->country
. I suggest to user a dot as separator to add "fake" nesting. I didn't find a good way to nest it natively without too many changes.Example:
factx['seller.country']
Steps to implement:
fields.yml
The text was updated successfully, but these errors were encountered: