Read filing's contents using specified encoding #1
Conversation
This file contains hidden or 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 `@encoding` instance variable on a `Filing` object is ignored in
methods such as `Filing#form_type`, which can lead to an `ArgumentError`
("invalid byte sequence in UTF-8"). The included test case demonstrates
such an error when we try to call `Filing#summary`.
This change takes `@encoding` into account when reading the filing from
disk, which avoids the `ArgumentError`.
Owner
|
Thank you, @myersjustinc! |
Author
|
No problem—thanks for merging it so quickly! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
(Copied from nytimes#86 as requested.)
The
@encodinginstance variable on aFilingobject is ignored in methods such asFiling#form_type, which can lead to anArgumentError("invalid byte sequence in UTF-8"). Before the included change inlib/fech/filing.rbis made, the included test case demonstrates such an error when we try to callFiling#summary.This change takes
@encodinginto account when reading the filing from disk, which avoids theArgumentError.(The entire test suite now only has three failing tests, two of which are addressed in nytimes#83 and the third of which also is related to mappings; none of those appears to be related to this specific change.)