Testing update of imports for v2 compatibility #78
Conversation
This file contains 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
mgreyo
force-pushed
the
v2compatibility
branch
2 times, most recently
from
41f4259 to
f6424cc
Compare
saley89
force-pushed
the
v2compatibility
branch
2 times, most recently
from
d744194 to
e9e4b1a
Compare
saley89
force-pushed
the
v2compatibility
branch
from
e9e4b1a to
336fca1
Compare
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.
For #77
@mgreyo and I took a very quick look into this and we believe it stems from not having
v2in the package naming. This needs further work to check and test it out.