Release v0.15.2

Changes

• check input values to avoid slice bounds out of range and similar (thanks @jerome-laforge for reporting issues)
• add fuzz tests for message.Unpack and for Decode method to all encodings
• assigned encodings like ASCII, Binary to specific type values, not Encoding interface

Release v0.15.1

Changes

• allow to create bitmaps of arbitrary size

This change can potentially break your code if you create a bitmap field.NewBitmap(...) and you set the its Length different than 8. Please, read more about change here #211

Release v0.14.1

Changes

• binary prefixes were added
• experimental emv package was added

thank you @FacundoMora @mfdeveloper508 @adamdecaf for your contributions and help!

Release v0.14.0

Changes:

• allow filtering output of the iso8583.Describe function
• apply a set of default filters to the iso8583.Describe

thanks @mfdeveloper508 for the contributions!

Release v0.13.2

add SetValue() method to binary, string, numeric fields (#199)

Release v0.13.1

field: nil check Numeric, String, Composite, etc accessors (#196)

* field: nil check Numeric, String, Composite, etc and add GetValue()

Issue: https://github.com/moov-io/iso8583/issues/195

* field: convert .Value into a safe data accessor

* update README

Co-authored-by: Pavel Gabriel <alovak@gmail.com>

Release v0.13.0

Changelog

BREAKING CHANGE

• remove Value field from String, Numeric, Binary fields and add Value() method instead (PR). This change makes code safer and addresses #195

Thank you @adamdecaf for your contributions!

Release v0.12.2

Changelog

• Fix variable length HEX prefix (#198)

Thank you @svz-ya, for the contributions!

v0.12.1

Changelog

• Add EBCDIC 1047 encoder & prefixer #190

Kudos to @Dakinola892 for the contributions!

Release v0.12.0

Changelog

• Introduce a SafeError type which is used to wrap around external errors, preventing the returned error message from displaying sensitive information, while still allowing errors to be matched (#185)
• Use SafeError type to wrap external errors in the field and encoding packages, as these operate on the potentially sensitive data. Errors from prefix and network packages were not changed since these only operate on the length part of the data, exposing their details should be okay. (#185)

Kudos to @cheukwing for the contributions!