HATEOAS-first backend framework.
No puede seleccionar más de 25 temas Los temas deben comenzar con una letra o número, pueden incluir guiones ('-') y pueden tener hasta 35 caracteres de largo.

TODO.md 1.4 KiB

12345678910111213141516171819202122232425262728
  1. - [ ] Integrate with other data stores
  2. - [ ] SQLite
  3. - [ ] PostgreSQL
  4. - [X] Access control with resources
  5. - [ ] Custom definitions
  6. - [ ] Middlewares
  7. - [ ] Request decorators
  8. - [ ] Status messages
  9. - [ ] Response bodies (in case of error messages)
  10. - [ ] Content negotiation
  11. - [X] Language
  12. - [X] Charset
  13. - [X] Media Type
  14. - [ ] Improve content negotiation on success/error responses (able to explicitly select language/media type/charset)
  15. - [X] HTTPS
  16. - [X] Date/Datetime handling (endpoints should be able to accept timestamps and ISO date/datetime strings)
  17. - [ ] Querying items in collections
  18. - [ ] Better URL parsing for determining target resource/resource IDs (e.g. `/api/users/3/posts/5`, `/users/3` is a query, `posts` is the target resource, `5` is the target resource ID. Different case with `/api/users/3/posts/5/attachments`)
  19. - [ ] Declare relationship (e.g. `/users/3/posts`)
  20. - [ ] Tests
  21. - [X] Happy path
  22. - [ ] Error handling
  23. - [ ] Implement error handling compliant to RFC 9457 - Problem Details for HTTP APIs
  24. - [ ] Create RESTful client for frontend, server for backend (specify data sources on the server side)
  25. - [ ] `EventEmitter` for `202 Accepted` requests (CQRS-style service)
  26. - [ ] Implement RPC endpoints
  27. - [ ] Implement `Vary` header (requires providing a `getHeader()` method in the request object to listen for obtained headers)
  28. - [ ] Add example on serving data as documents using `application/html` type.