[WIP] Improve serialization also for legacy database versions#113
Open
[WIP] Improve serialization also for legacy database versions#113
Conversation
97c743d to
a770ec4
Compare
Pull Request Test Coverage Report for Build 674
💛 - Coveralls |
41d0506 to
cb7c7d7
Compare
Member
Author
|
See #53 for conversation. |
70f374c to
c03c7eb
Compare
Codecov Report
@@ Coverage Diff @@
## master #113 +/- ##
==========================================
- Coverage 92.4% 67.3% -25.11%
==========================================
Files 32 34 +2
Lines 3726 6578 +2852
==========================================
+ Hits 3443 4427 +984
- Misses 283 2151 +1868
Continue to review full report at Codecov.
|
f6cbdf5 to
a300130
Compare
a300130 to
250fb56
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
Other information