Florida API Parsers#1842
Open
MorganBennetDev wants to merge 25 commits intomainfrom
Open
Conversation
Define schema of API results for Florida to allow Pydantic validation
Basic setup defining the API endpoints we're using and their expected output types.
Implement some perhaps overly generic scaffolding for scrapers and parsers, which will hopefully make things easier in the future.
It is not relevant to the parsers and will be handled later.
So many docstrings...
Contributor
|
I like it! I appreciate that the majority of this is Pydantic models and validators with some aliases to map to internally reasonable names. I like that we can also subclass these models with |
ID mapping will not be complete yet as I don't know every court name in the system.
Refactor is for a different PR
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Resolves #1782
I still need to create IDs for Florida courts and use them in output instead of the internal Florida IDs and do a little post-processing to extract transfers and other data. However, this is mostly complete so I'd like to get review started a bit early.
Summary
Add Pydantic dependency to simplify JSON data validation and parsing.
Create base classes for parser outputs to guarantee certain data is always present.
Create a slightly modified parser base class.
Create parsers for Florida case list, case info, case party list, case docket entry list, and courts endpoints.