Expose interpretOptions so that custom HasInterpretOptions instances can be created #13
Conversation
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
phadej
suggested changes
Feb 4, 2020
…can be created. Bump version from 0.3 to 0.3.1 for this non-breaking change.
AJChapman
force-pushed
the
allow-interpret-options
branch
from
4afba08 to
a0bde31
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The point of
HasInterpretOptionswould appear to be that you can implement your own instance of it. But it is impossible to implement a customHasInterpretOptionsinstance becauseinterpretOptionsis not exposed.