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.

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

Do not double serialize YAML in Legacy Repository #348

Merged
merged 4 commits into from
May 6, 2018
Merged

Conversation

mostlyobvious
Copy link
Member

@mostlyobvious mostlyobvious commented May 6, 2018

See #345

1. Append events on 0.18.2 schema and gem version in separate process.
2. Read using current version of legacy event repository.

Testing on client level to ensure default configuration changes (like
used mapper) breaking compatibility will be caught.

Also added event writing scenario that in contrast works, showing that
issue does not manifest when operating on newly-written data only.

[#345]
Probably missed as early as #168. Did not have a chance to show up until
repository stopped handling serialization itself (now it's the client).

[#345]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant