Closed arjunrajinstaclustr closed 2 years ago
Sorry, mistook the error message I posted above for a missing identifier on the path, whereas it is complaining about a missing identifier on the response schema. I have already mentioned possibly skipping the identifier requirement for the listable data sources on #328, so closing this issue.
Is your feature request related to a problem?
Listable data sources (GET requests) that are not tied to a CRUD resource should not require a resource identifier.
Example use case - "Get all posts created by my user". In such a case, the authorization mechanism (eg - API key) for the API would identify the user.
Describe the solution you'd like
Same as acceptance criteria.
Acceptance criteria
Error: could not find any identifier property in the resource schema definition
Describe alternatives you've considered
Workaround is to structure the endpoint path to contain a redundant identifier.
Additional context
Add any other context or screenshots about the feature request here.
Checklist (for admin only)
Don't forget to go through the checklist to make sure the issue is created properly: