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

resp_tidy() #40

Closed
jonthegeek opened this issue Dec 25, 2024 · 1 comment · Fixed by #43
Closed

resp_tidy() #40

jonthegeek opened this issue Dec 25, 2024 · 1 comment · Fixed by #43

Comments

@jonthegeek
Copy link
Owner

Add a function (tentatively resp_tidy()) for use with httr2::resps_data(). It takes a response, extracts its individual tidy function (and, optionally, arguments), and processes the data using that function.

I might want to do this as a generic, but right now all the implementations I can think of would likely use the default, so don't over-complicate things yet.

@jonthegeek
Copy link
Owner Author

I went ahead and over-complicated! I think it eliminates the need for resp_parse(), but I'm not killing that quite yet.

jonthegeek added a commit that referenced this issue Jan 10, 2025
Potential breaking change: Functions that accept lists of responses (ie `resp_parse()`) now use the argument name `resps` to clarify documentation difference from `resp`. I don't think anything calls that function directly, though, so it probably won't impact even me.

Also added `resp_body_auto()`, `resp_body_csv()`, `resp_body_tsv()`, and `resp_body_separate()` to help parse response bodies.

Closes #40.
jonthegeek added a commit that referenced this issue Jan 10, 2025
Potential breaking change: Functions that accept lists of responses (ie `resp_parse()`) now use the argument name `resps` to clarify documentation difference from `resp`. I don't think anything calls that function directly, though, so it probably won't impact even me.

Also added `resp_body_auto()`, `resp_body_csv()`, `resp_body_tsv()`, and `resp_body_separate()` to help parse response bodies.

Closes #40.
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

Successfully merging a pull request may close this issue.

1 participant