Case insensitive ends with on EndsWith #21
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
|
The build failed, but when I clicked on details Travis claimed that this wasn't an active project??? |
|
I deactivated it because it should never have been trying to build this on Linux (AFAIK). The build relies on "Excel.dll" which AFAIK is only available on Windows. |
|
@dsyme Thanks, that makes sense. |
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 ran into an inexplicable
NullReferenceExceptionwhen trying to load an XLSX file that I used ".XLSX" in the file path for theExcelProviderconstructor. It wasn't until I ran it locally that I discovered the problem was a case sensitive call toEndsWith(). This fixes that.