Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix incorrect message in serializer tokens and correctly implement next_entry_seed #1918

Merged
merged 2 commits into from Jan 23, 2021
Merged

Fix incorrect message in serializer tokens and correctly implement next_entry_seed #1918

merged 2 commits into from Jan 23, 2021

Commits on Oct 27, 2020

  1. Fix incorrect messages in serialized tokens assertions 

    Serializer contains expected tokens, called methods provide actual tokens
    @Mingun
    Mingun committed Oct 27, 2020
    Copy the full SHA
    920a77a View commit details
    Browse the repository at this point in the history

  2. Forward Readable|Compact next_entry_seed to underlying next_entry_see… 

    …d instead of usage of default implementation

Difference is noticeable for deserializers that rely on call of next_entry_seed
(for example, current quick-xml supports only next_entry_seed)
    @Mingun
    Mingun committed Oct 27, 2020
    Copy the full SHA
    97c350a View commit details
    Browse the repository at this point in the history