Skip to content

Conversation

@ScottDugas
Copy link
Collaborator

No description provided.

Most of the time this will be used with remainders, so make most
of the tests cover that
I left a TODO for myself to add unit tests of withRemainder...
I updated the tests to not use KeyValue directly, at which point,
having DataInKeySpacePath expose the value and not the raw KeyValue
seemed to make sense
This isn't the greatest test, but I think the proper test would
be to explicitly list the non-default methods and then use reflection
and error if any new methods are added and don't have a default
implementation.
Predominately:
- DataInKeySpace now errors if it gets a null value
- Improved javadoc linking KeySpace.resolveFromKeyAsync and
  KeySpacePath.toResolvedPathAsync
- Fix error message in default method
- Reduce visibility of ResolvedKeySPacePath.withRemainder
- new negative tests in DataInKeySpacePathTest
- Better coverage of exporting with mixed-type sub-directories
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