Do not parse charges on Record parser about recordexpungpdx HOT 6 CLOSED

@nwalton125 Hey! This task hasn't been updated in a few months so I just wanted to check in and see how it's going. Are you still working on this task? If not, or if I don't hear back, I will open it up for someone else to work on.

from recordexpungpdx.

from recordexpungpdx.

@nwalton125 no worries! Thanks for the reply :)

from recordexpungpdx.

@maxkwallace I added a temporary fix to this in another commit. It still parses the charges, but it doesn't save the results. We could probably close this issue?
It's not so important, but what I would actually like to see done is a complete re-write or refactor of the record parser so that it is easier to understand. What do you think?

from recordexpungpdx.

@NickSchimek sounds good, I'll close the issue.

Regarding the refactor I'd have to read the parser code myself in order to comment. I trust your judgment. There are a lot of factors that go into deciding whether a refactor makes sense but IMO the main ones are (1) whether the code is functioning well now and (2) whether or not it will need to be edited many times in the future.

from recordexpungpdx.

@maxkwallace yeah, I completely agree. It most likely will not have to be edited in the future, and it currently works so.... It was just something that would be nice, but is not currently necessary.

from recordexpungpdx.