oxidecomputer / oxidecomputer/third-party-api-clients
Mailchimp fields value not comma separated
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 150
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
Mailchimp: It looks like all api methods that take a fields value in the Mailchimp client do a .join(" ") vs a .join(","). The Mailchimp api specs out fields as a comma separated list not a space separated list.
I'd be happy to help fix this but am unclear if the clients are auto-generated vs manually patched here
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the Mailchimp client methods that accept a fields value and inspect how those clients are generated or patched. Confirm the API specification and identify the relevant test coverage; the work is done when every applicable fields value is comma-separated and the behavior is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100