Adding some aggregation endpoints #8
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I was assuming a
resources
collection might accommodate multiple resource types, then resources can be classified by type throughfacility_code
.Examples:
I would prefer to use
endpoint
instead offacility_code
(i.e something like/api/waterpoints/values/region
instead of/api/wp001/values/region
) for the sake of consistency & prettier URLs but I haven't figured how to do that without an extra database query unless facility_code values are equal endpoints. Is there a more convenient way to resolve this or should I just assume there will be one resource type per instance?