Add Static Casings Map & LC Nav Assembly #20
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
cybersonic
added a commit
that referenced
this pull request
Feb 25, 2015
Add Static Casings Map & LC Nav Assembly
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.
I used your data from issue #19 to create a static casings map, which is used to map function names. It seemed like a better idea to keep that as a JSON file that could be updated by the community as necessary (I found one new ORM function, for example, that wasn't in yours and added it). I'm only using one of the struct keys at the moment, but they are all there for future use.
I've also converted the alphabetical navs to lower case so to ensure UC first character function names won't create separate nav elements.