Add a backend API
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 20
- Forks
- 22
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 4
Description
Should we deploy our own backend so that we don't rely on CHHS Open Data Portal?
The WIC vendor location functionality depends on their CKAN API, which changes periodically (see #25, #50, #56). The resource key in the URL appears to update whenever new data is published.
In addition to locations, our backend could serve our own version of the WIC Authorized Product List. We currently rely on sample_data/foods.json.
The main trade-off is increased system complexity. A proof-of-concept monorepo is available here for review: https://github.com/natebass/wicit-doc-example.
Contributor guide
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
Start by reviewing issues #25, #50, and #56 to understand the CKAN API changes, then inspect the linked proof-of-concept monorepo. Compare the proposed backend with the current sample_data/foods.json and vendor-location flow. Done means reaching a documented decision on whether and how to pursue the backend.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100