Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

allow for users to the command line tools without having a database #60

Open
alpiazza13 opened this issue Nov 10, 2020 · 1 comment
Open

Comments

@alpiazza13
Copy link
Collaborator

alpiazza13 commented Nov 10, 2020

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).

@alpiazza13 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 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
@mscarey
Copy link
Collaborator

mscarey commented Mar 28, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants