Fix MatchError when no Styles Exist for Cell #95
Merged
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.
This address #94
This fixes an error when no styles exist for a cell and we were getting a MatchError due to assuming that Enum.filter call in
sax_event_handler
would always return at least one element. To fix the error, we're a little safer when handling the result ofEnum.filter
if a tuple is returned, continue with the existing happy path. In the case that nothing is returned, we simply append a'0'
to indicate that there are no styles for that current cell.Changes:
Xlsxir.ParseStyle.sax_event_handler/2
- Safer handling of valuesXlsxir.ParseWorksheet.find_styles/2
- Safer handling of expected values