Unfortunately this didn't work for me, the tool still behaves as if there was no quoting:

edgar-tool text_search '"Tsunami Hazards"'

makes requests to: https://efts.sec.gov/LATEST/search-index?q=Tsunami+Hazards (note the lack of url encoded quotes)

@GalenReich Ahh my bad. I just ran through it with a debugger and figured it out in 549273e

In order to make the debugger easy to use I had to rename main.py to __main__.py and run the directory as a module. I kept those changes in this commit because I think it makes the code easier to work with locally, and has no effect for users running it as a script.

Those changes will fix the issue for now. Users will need to wrap their already quoted phrase in another single quote, like in your example (edgar-tool text_search '"Tsunami Hazards"'). But, it would be friendlier if we could allow users to just use quotes once, like this:

edgar-tool text_search "John Doe" Pharmaceuticals Chemicals

We can't because of an issue related to how fire interprets the command line arguments, and then how those arguments are parsed before the call to urlencode.

For example, if I call the CLI without using the single quote then double quote pattern, '"..."'

edgar-tool text_search "John Doe" Pharmaceuticals Chemicals

Then keywords equals ('John Doe', 'Pharmaceuticals', 'Chemicals') in SecEdgarScraperCli.text_search

Which is then joined into the single string 'John Doe Pharmaceuticals Chemicals' in EdgarTextSearcher._generate_request_args here:

We can fix this so that the code understands that a string with a space character, like 'John Doe' but not 'Pharmaceuticals', should be parsed as an exact phrase. I can do this in a follow-up PR.

The desired behaviour is that a search for "Tsunami Warning" will give requests where q=%22Tsunami+Warning%22

At the moment there is some double escaping going on and (in Powershell) the space is doubly escaped, but the quotes are missed: q=Tsunami%2520Warning

You've given me some ideas about solving this at the join - I'll push a commit or two in a sec

I think that solves it - the machinery was already mostly working because of the urlencode here:

Those changes implement your suggestion of wrapping space-containing keywords in quotes, which also solves the escaping problem. Thanks for pointing out how fire parsed the keywords - super helpful!

Let me know what you think!

@GalenReich haha man, it's your repo! If you think the PR is good to go then merge away 😎

I'll take a closer look at your commits tomorrow - but I trust ya! Im embarrassed that I didn't actually solve the issue and encoded the URL twice. I code like sh*t without TDD. It's my kryptonite.

Converted to a draft while I flesh out the URL generation code. Will wrap this up in the coming days.