API Breaks
- Remove the
BinaryFragment.Datafield and replace it withBinaryFragment.RawData, which contains the decoded but still compressed data from the fragment. Clients should use theio.Readerreturned by the newBinaryFragment.Data()method to access the uncompressed data. (#76) Apply()andBinaryApplier.ApplyFragment()enforce a default maximum binary fragment size of 100 MiB. Clients may adjust or disable this limit by passing theWithMaxBinaryFragmentBytesoption to their apply calls. (#77)
Improvements
- Short source files are reported as conflicts instead of EOF errors during applies (#63)
- Clients can limit the size of binary fragments during applies using the
WithMaxBinaryFragmentBytesoption (#77) BinaryFragment.String()returns the same content lines as were originally parsed (assuming normalized whitespace) instead of an equivalent encoding that parsed to the same value but was not the same text (#76)