Random ideas for LoopBack

todo.md

Ideas I discovered on the internet but don't have time to pursue.

Run todo-example tests against PostgreSQL

• a new Travis Job, we need a new Pipeline
• https://travis-ci.community/t/job-labels-name-improvement-proposal/79
• https://docs.travis-ci.com/user/build-stages/

Contribute LoopBack monorepo definition to RenovateBot

Hot Module Replacement

• https://docs.nestjs.com/techniques/hot-reload

Danger systems

• https://danger.systems/js/usage/culture.html
• https://hackernoon.com/dont-be-the-bad-cop-in-pull-request-reviews-let-software-do-that-job-1eb9e574c2d1
• celebrate patches removing more lines than adding
• automatically assign labels to PRs based on files changed
• post a comment when a CI build failed
• ?modify Coveralls config to post comments when coverage goes down?

A better app.route API:

app.route({
  @intercept('log')
  @get('/foo/bar')
  @response(...)
  async handle(
    @param.path() id: number,
    @inject.getter('current-user', {optional: true})
    currentUser?: UserProfile,
  ) {
    // ...
  }
})

https://docs.pact.io for consumer contract testing - perhaps replace http-service-proxy?