Keith Salzman

I vote for typescript-eslint and a modified version of prettier.

You make a very good point @skosito. You have convinced me, albeit reluctantly, to adopt default options for both the linter and prettier.

> This should be committed under the `bri/` directory along with the other reference implementations... @kthomas are you referring to the examples/bri-1 directory? If so, what is the difference between...

[NestJS Scope hierarchy](https://docs.nestjs.com/fundamentals/injection-scopes#scope-hierarchy) The REQUEST scope bubbles up the injection chain. A controller that depends on a request-scoped provider will, itself, be request-scoped. Imagine the following dependency graph: CatsController

More Resources: [Sequential Operations](https://www.prisma.io/docs/concepts/components/prisma-client/transactions#sequential-prisma-client-operations) [Interactive Transactions](https://www.prisma.io/docs/concepts/components/prisma-client/transactions#interactive-transactions)

> What is the issue if the controller ends up request scoped because an agent injects a dbContext which is also request scoped? For a request-scoped controller, a new instance...

Update on this issue: 1. Current work done on [prisma transactions branch B](https://github.com/eea-oasis/baseline/tree/feature/741B-prisma-transactions) 2. There are known issues when doing a prisma transaction and creating two entities in the DB...

I think enabled properly here means that the cors setting only allow exactly our expectations within requests - Testing could be run through calls that adhere or not to cors...