new feature: default column headers can now have different naming methods #13
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
|
ok thanks for comments, I'll close / reopen. |
|
You didn't need to close it, just make the changes and push them (and rebase if you really want to clean the git history) |
|
can't figure out why TravisCI is throwing my PR. any idea? |
|
It happens sometime, probably a race condition somewhere that I haven't identified yet. Don't mind it much, there was a build that passed so it's 🆗 for me. Anyway, thanks for taking care of that. |
abe33
added a commit
that referenced
this pull request
Oct 21, 2015
Add new default columns naming strategies
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 am editing a 130+ columns file whose column definition is in a separate file, with numeric indexes. converting "EC" to 133 was not straight forward :)