Extract mapper for Transmodel bookWhen
, new values for relativeDirection
#6393
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.
bookWhen
@t2gran had to fix a bug I introduced in #6385 which I feel a bit bad about. In order for this to not repeat itself I extracted a mapper for the field in question and added lots and lots of tests.
The line coverage in the mapper is 100% and the branch coverage 93%.
New enum values for Transmodel's relativeDirection
In #6343 we introduced a new internal enum value for RelativeDirection. We don't want to expose the type ever in the API so I introduced mapper to get rid of it. In that process I noticed that there are unmapped enum values in the Transmodel API, which I also mapped away.
@t2gran has requested that instead we add the enum values to the API which I did.
There was already a test for the enum serialisation which also tests the new values.
Issue
Relates to #6384
Unit tests
Added.
Documentation
Javadoc.