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

Move endpoints for lists into their own file #45

Open
hepplerj opened this issue Jul 27, 2022 · 0 comments
Open

Move endpoints for lists into their own file #45

hepplerj opened this issue Jul 27, 2022 · 0 comments
Assignees
Labels
enhancement New feature or request question Further information is requested

Comments

@hepplerj
Copy link
Member

Right now for the Bills of Mortality, we have three lists of data that are used for populating the UI and filtering data as users select them:

  1. Parishes (distinct)
  2. Causes of death (distinct)
  3. Christening descriptions (distinct)

Parishes has its own endpoint, but Causes and Christenings exist within their respective files (bom-causes.go and bom-christenings.go). Just to make this a bit easier for our mental model of how the endpoint works, I may move these into a new b om-lists.go file that accepts query parameters that returns the specific list. Instead of /bom/parishes returning a list of parishes, we might have something like /bom/lists?type=parishes and so forth.

@hepplerj hepplerj added enhancement New feature or request question Further information is requested labels Jul 27, 2022
@hepplerj hepplerj self-assigned this Jul 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant