Open 4ndygu opened 3 years ago
Also tagging @jcushman for visibility.
Thanks @4ndygu!
This looks OK to me at a skim, though tests seem to be failing.
@flooie will you give it a final review once tests are working?
Hi @mlissner! sorry for the late response, and my bad -- it seems like I may have included some of the regex patterns in the examples page, which polluted the tests. These should be updated now!
This should be back to you, then, @flooie.
@4ndygu this looks great. Thank you for adding your two cents. I hope to give this a deeper look tomorrow.
@mlissner also if I remember correctly, we haven't completed regex patterns for every example permutation yet, so I don't think @4ndygu additions caused that test to fail.
Hi @flooie! Just to clarify, might be my bad here -- i think the error arose because I accidentally added two patterns to the examples
section as opposed to regex, which would have caused the existing regex patterns at the time to fail.
That sounds like it would cause the fail for sure.
On Jul 12, 2021, at 5:39 PM, Andy Gu @.***> wrote:
Hi @flooie! Just to clarify, might be my bad here -- i think the error arose because I accidentally added two patterns to the examples section as opposed to regex, which would have caused the existing regex patterns at the time to fail.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.
Hi there! I am currently mining some of the data in the Caselaw Access Project API, and we noticed that some of the Regex patterns in
courts.json
do not match the courts displayed in api.case.law/v1/courts/. This pull requests takes a subset of the most frequently seen courts in CAP and adds those court names to the Regex pattern of the underlying dataset.