Conventions should not affect mongodb serialization #43
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Assume an application that uses Horarium have code like this:
Such code can be used to adjust the application's MongoDB document, but accidentally changes Horarium's internal representation of enum
Status
. Jobs serialized with different conventions are not compatible.This behavior discovered after #41 lazy MongoDB access. With lazy MongoDB access, the app has time to register conventions. That leads to different serialization with lazy and without lazy access.
PR sets Horarium's field names and types explicitly to always match default conventions.
Also, minor typos fixed.