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
Then they'd just get the JSON output. As of now it'll throw an error if there's no database set up. Probably want this to be a command line option similar to --showbrowser. Update the readme as appropriate after doing this. May only apply to parse_filings, parse_hearings, and parse_settings (not sure it makes sense to run the schedule without a database since that doesn't output any json files, and same with get_filings_settings_since_date, although a future issue could be to make them do that).
The text was updated successfully, but these errors were encountered:
alpiazza13
changed the title
allow for people to run parse_hearings, parse_filings, parse_settings scripts without having a database
allow for users to run parse_hearings, parse_filings, parse_settings scripts without having a database
Nov 10, 2020
alpiazza13
changed the title
allow for users to run parse_hearings, parse_filings, parse_settings scripts without having a database
allow for users to the command line tools without having a database
Nov 11, 2020
I added --db / --no-db flags to the parse_hearings and parse_settings command line interfaces. These still need testing, and there are other command line interfaces in the repo. It would help to know if all the CLIs are needed by the users, or if there are some that can be cut.
Then they'd just get the JSON output. As of now it'll throw an error if there's no database set up. Probably want this to be a command line option similar to --showbrowser. Update the readme as appropriate after doing this. May only apply to parse_filings, parse_hearings, and parse_settings (not sure it makes sense to run the schedule without a database since that doesn't output any json files, and same with get_filings_settings_since_date, although a future issue could be to make them do that).
The text was updated successfully, but these errors were encountered: