GitHub - johncmunson/todo-api: Playing around with Objection.js, Knex, Express, and SQLite. Also, seeing how well-suited Jest is for writing integration tests.

Todo:

standardize on module.exports = { a } rather than module.exports = a
add error responses to openapi.yaml
- probably just need the common ones like 404, plus a default
- not feasible to document all possible error responses
nodemon dev server
consider using this approach to loading dotenv config instead of requiring dotenv in multiple spots in the source code
- https://github.com/motdotla/dotenv#preload
write unit tests and strive for 100% test coverage
- may need to use separate jest configurations for unit/integration tests. this can be accomplished with the --config cli flag
version the api
setup the standard tooling for a Node project
- eslint
- prettier
- husky (run tests + eslint + prettier as githooks)
update openapi.yml with the /tags endpoints, and the new functionality related to the "relations" query parameter
castValues only supports top level values, but now that relational data is supported it might need to become recursive
might need to define schemas in a separate directory (perhaps inside of models) so that they can be composed together inside static get jsonSchema. Another option is to try calling Category.jsonSchema inside of Todo.jsonSchema
- Vincit/objection.js#478 (comment)
Add the ability to create todo/tag associations

Reading:

Name		Name	Last commit message	Last commit date
Latest commit History 57 Commits
db		db
middleware		middleware
migrations		migrations
models		models
routes		routes
seeds		seeds
tests		tests
utils		utils
.gitignore		.gitignore
LICENSE.txt		LICENSE.txt
README.md		README.md
Todo API.postman_collection.json		Todo API.postman_collection.json
index.js		index.js
jest.config.js		jest.config.js
knexfile.js		knexfile.js
openapi.yaml		openapi.yaml
package-lock.json		package-lock.json
package.json		package.json

johncmunson/todo-api