1.2.0

What's Changed

• Update unkown details to not add an instance variable by @lauragilgz in #29

Avoid adding unknown details as instance variables to avoid unexpected errors when a unvalid format is passed. They are still accessible through details.unknown

Full Changelog: 1.1.1...1.2.0

1.1.1 minor fixes

CHANGELOG

Fixes

• safe parse some banks empty character operation details codes

Full Changelog: 1.1.0...1.1.1

1.1.0

CHANGELOG

Fixes

• Don't override operation.details.{detail_code} if there are lines with the same detail_code
• Add safe operator for IBE and IPY in case of missing data

New Features

• Added support for unknown detail types. If a detail_code is unmapped, its data will be added to a hash which can be accessed through operation.details.unknown with the format detail_code: line.detail.

Full Changelog: 0.0.7...1.1.0

1.0.0

CHANGELOG

⚠️ Breaking Changes

• unified access to details: This release introduces a significant change in how details are accessed. You must now use operation.details to retrieve all attributes. To access a specific attribute, use the syntax operation.details.attribute. For instance, to get the structured_label, use operation.details.structured_label
• addition labels (LC2, LCC, LCS, LIB) are no longer appended to the operation label
• additional references (RCN, REF) are no longer appended to the operation reference
• operation.original_amount is not signed anymore
• multiple LIB lines are appended with line breaks to operation.details.free_label

New Features

• Expanded details support: added support for additional detail types, including NPO, IBE, NBU, and IPY.
• You can now access the raw data (70 characters) of each detail line by it's code using operation.details.npo.

Full Changelog: 0.0.7...1.0.0

0.0.7

bump version

0.0.6

Add `exchange_rate` to operation (#12)

0.0.5

do not make assumptions on fee signs (#11)