You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Parser logic is failing due to docket formatting differences. It appears most dockets have indentations with white space inside each charge. Outlier case has a docket with left alignment on the charges section. This difference in alignment throws the parsing off and the "Offense Date" is parsed in the "Severity" section. The flag checking the severity of the charge then fails because the array returns empty of key words.
Reference docket: Axxxx xxxxx6862
The text was updated successfully, but these errors were encountered:
Issue: #174
Problem: Parser doesn't always parse what's needed.
Solution: Completely restructure the parsing file to use mostly just Regex.
Before:
File would parse line by line
Use minimal regex to determine how to display info in line
After:
File parses in chunks based on regex
Iterates over multiple similar chunks
Uses a lot of regex to refine search on those chunks
Note: I wanted to add some extra stuff, but I feel like it's best to push something that works, rather than try and perfect it. I modified the test a bit. My code passes the test now. I would still like someone to review with me and make sure I've covered all the defaults. I'm afraid that not everything has been covered in the test, and so I may have missed something.
Parser logic is failing due to docket formatting differences. It appears most dockets have indentations with white space inside each charge. Outlier case has a docket with left alignment on the charges section. This difference in alignment throws the parsing off and the "Offense Date" is parsed in the "Severity" section. The flag checking the severity of the charge then fails because the array returns empty of key words.
Reference docket: Axxxx xxxxx6862
The text was updated successfully, but these errors were encountered: