bug introduced in PR #1192 resolved #1196
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
Closed
|
@0xfe @mscuthbert this one is minor it should be a minute to merge it. |
|
Merged. As far as CamelCase vs ALL_CAPS: I'm usually in favor of the former if it makes any sense to ever alter their values at all. But Tables is functioning like a giant |
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.
minor bug resolved.
I saw it while cosidering if the members of
Tableshould me camelCase. ie.:Table.stemWidthrather thanTable.STEM_WIDTH. @0xfe what is your preference?Tableis now internal.