Ryan Parker

I see now, that worked. This is a little confusing especially since the law list API returns two `number` props and neither are the exact number needed for the details...

It might be worth mentioning how the number required by the law details API must be extracted from the `bills[x].laws[y].number`. It might also be useful to add a `url` for...

Thanks for the help @apreiter18, One last thing. It would be nice if the API returned 404 instead of 500 if the law number does not exist like the example...

Sorry for the back to back issues. I've recently improved some validation logic in my work and it's helped identify some interesting issues.

Here's a list of all the duplicates that i've caught in the 118th congress: ``` - hrpt-416 - hrpt-414 - hrpt-413 - hrpt-412 - hrpt-411 - hrpt-410 - hrpt-409 -...

Looks like all the previously mentioned reports for the 118th are fixed. However I caught a few other duplicates on past congresses: > Ids are in the format `{type}{number}-{part}` e.g....

Here's a curl for the 117th duplicate. (offset: 934) ```sh curl --location 'https://api.congress.gov/v3/committee-report/117?format=json&offset=934&api_key=' ```` Response (see `"citation": "S. Rept. 117-39"`, `"citation": "S. Rept. 117-39,Errata"`) ```json { "pagination": { "count": 1019,...

That makes sense, however from an API perspective this seems a bit odd. If it's a correction of SRPT 39 then It seems like something that should be part of...

This is occurring again for the same member `M001200`. I also noticed George Santos (`S001222`) was recently marked `"currrentMember": true` as well.

It looks like this may have been fixed however it may have introduced a new bug. It looks like when `currentMember` is set to false the API does not return...