GEODE-9449: Remove 'b' prefix from constants #7118
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
Kris-10-0
requested review from
DonalEvans,
dschneider-pivotal,
jdeppe-pivotal,
kirklund,
nonbinaryprogrammer,
ringles and
upthewaterspout
as code owners
dschneider-pivotal
approved these changes
Nov 17, 2021
nonbinaryprogrammer
approved these changes
Nov 17, 2021
Removed 'b' prefix on all byte arrays and added "_STRING" to string constants.
Kris-10-0
force-pushed
the
feature/GEODE-9449
branch
from
c5109ce
to
065f8ca
Compare
ezoerner
pushed a commit
to ezoerner/geode
that referenced
this pull request
Mar 12, 2022
Removed 'b' prefix on all byte arrays and added "_STRING" to string constants. Co-authored-by: Kristen Oduca <koduca@Administrators-MacBook-Pro.local>
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.
Removed 'b' prefix on all byte arrays and added "_STRING" to string constants.
For all changes:
[ x] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?
Has your PR been rebased against the latest commit within the target branch (typically
develop)?Is your initial contribution a single, squashed commit?
Does
gradlew buildrun cleanly?[NA] Have you written or updated unit tests to verify your changes?
[NA] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?