Merge branch 'main' into feat/mongo-db

kordis-leitstelle · Apr 16, 2023 · 706444a · 706444a
2 parents df36121 + e58bf02
commit 706444a
Show file tree

Hide file tree

Showing 3 changed files with 43 additions and 36 deletions.
diff --git a/...ecture-decisions/adr004-graphql-schema.ms → ...ecture-decisions/adr004-graphql-schema.md b/...ecture-decisions/adr004-graphql-schema.ms → ...ecture-decisions/adr004-graphql-schema.md
@@ -6,16 +6,22 @@ accepted
 
 ## Context
 
-Apollo GraphQL offers 2 approaches to create and maintain a GraphQL schema: Code First and Schema First. We have to choose one of them to start developing our Graph.
+Apollo GraphQL offers 2 approaches to create and maintain a GraphQL schema: Code
+First and Schema First. We have to choose one of them to start developing our
+Graph.
 
 ## Decision
 
-We are using the Code First approach which generates a GraphQL schema from TypeScript classes and their annotations.
-With the Code First approach, we have type safety out of the box and we can generate the schema automatically.
-Furthermore, the knowledge about GraphQL schema specifications is rare in the team, which also contributed to this decision.
+We are using the Code First approach which generates a GraphQL schema from
+TypeScript classes and their annotations. With the Code First approach, we have
+type safety out of the box and we can generate the schema automatically.
+Furthermore, the knowledge about GraphQL schema specifications is rare in the
+team, which also contributed to this decision.
 
 ## Consequences
 
 - It is easier to setup, maintain and refactor.
-- We can think in TypeScript models and types while developing our schema, which should enable us to develop faster.
-- We might hit a barrier which we currently can not see with the Code First Approach when our schema gets complex.
+- We can think in TypeScript models and types while developing our schema, which
+  should enable us to develop faster.
+- We might hit a barrier which we currently can not see with the Code First
+  Approach when our schema gets complex.
diff --git a/package-lock.json b/package-lock.json
diff --git a/tools/db/README.md b/tools/db/README.md
@@ -7,8 +7,9 @@ running on your maschine.
 ### Test Data
 
 The data for the test database is within the [`data`](./data/) folder. If you
-want to create a new collection, use the [`template.ts`](./data/template.ts) as a starter for your
-file. The naming of the file should be `<collection name>.data.ts`.  
+want to create a new collection, use the [`template.ts`](./data/template.ts) as
+a starter for your file. The naming of the file should be
+`<collection name>.data.ts`.  
 Please adjust the test data in your branch if you introduce migrations!
 
 ### Start