Fix CoordinateReferenceSystem naming #2422
Merged
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
|
@Lojjs as name change has been merged into the internal dev branch; dev, and I presume a lot of other builds, are probably failing because of this oversight of mine. Hopefully you'll see this otherwise trivial change, and freely merge it if you are happy with it. I have grepped the repo, this should be all the usages fixed; and in these cases, I believe it does make sense to use the internal names (at least until we can figure out a better "public" way) |
MishaDemianenko
approved these changes
Jan 7, 2022
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.
CoordinateReferenceSystemhas changed it's internal naming. #2417 fixed the internal Neo4j build error; however, it was masking these additional usages. I should have double checked if there were more usages when investigating previously.