Map start position #137
Merged
Map start position #137
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
bcardarella
force-pushed
the
bc-map-start-position
branch
4 times, most recently
from
65086fa
to
e593f93
Compare
bcardarella
force-pushed
the
bc-map-start-position
branch
from
e593f93
to
cdc12e3
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.
Currently just a failing test as I'm not sure if this is by design or not. If there is some reason why maps start positions are not supposed to start at the
%instead of the{let me know. If this is a bug I'm happy to look into the solution but just want to confirm this is infact a bug first.