Release v0.8.4

What's Changed

• added a missing rightPadder to JSON spec builder by @adamdecaf in #156

Full Changelog: v0.8.2...v0.8.4

Release v0.8.3

Extend MTI enum (#153)

* Add Reversal Request Response to MTI enum

* Add 0180 and 0190

* Add administrative messages

* specify that 0180 is positive

* fix whitespace

Co-authored-by: louis <[email protected]>

v0.8.2: Extend MTI enum (#153)

Changelog

• Extend MTI enum (#153) (add reversal response, administrative messages, network management, etc.)

Release v0.8.1

Changelog

• Fix issue with packing zero length fields #149
• Add Clone() method for iso8583 message #150

Release v0.7.0

Changelog

• Replace %v with %w in error messages (#152)

Release v0.6.8

Changelog

• Fix BCD decoding to limit number of bytes being read from source #137

Release v0.6.7

Changelog

• Use = as default the separator in Track 2 #135

Release v0.6.6

Changelog

• Support 'D' separator in Track 2 #134

Release v0.6.5

Changelog

Various encoding / decoding fixes:

1. all field.JSONUnmarshal methods now unquote values using the json.Unmarshal rather than using strconv.Unquote. This is because the json.Unmarshal function is more robust and handles a wider range of edge cases.
2. field/Binary MarshalJSON and UnmarshalJSON returns hex based strings and takes them in respectively. Previously, they handled bas64 representations of bytes making them pretty unusable in their string formats. This should be regarded to be a breaking change even though the API itself is unchanged.
3. field/Bitmap no longer supports JSON encoding / decoding. The decision was made to do this because bitmaps add little value in JSON form and are used specifically for the parsing of ISO8583 messages with no business use case.
4. field/Composite now lazily creates subfields only if they are being packed or unpacked rather than creating all subfields when defined in the spec regardless of whether they are to be populated with values or not. This change was necessary to ensure that only relevant fields are populated in their JSON format. Before, even unpopulated fields were populated with "" or null values. This caused issues when unmarshalling in that JSON representation back into the iso8583.Message.
5. Replace spec.CreateSubfields with field.CreateSubfield. Due to the change in how Composite now creates fields, we needed to change the function signature of this function.

Release v0.6.4

Changelog

• Added Track Data support (track 1, track 2, track 3) #124