@tech4good/angular-schematics 18.0.2 → 18.0.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (27) hide show
  1. package/README.md +0 -1
  2. package/package.json +1 -1
  3. package/src/entity/files/__name@dasherize__/__name@dasherize__.store.ts.template +1 -1
  4. package/src/entity/index.js +1 -1
  5. package/src/entity/index.js.map +1 -1
  6. package/src/init/files/.gitignore.template +3 -0
  7. package/src/init/files/CODE_OF_CONDUCT.md.template +51 -0
  8. package/src/init/files/CONTRIBUTING.md.template +298 -0
  9. package/src/init/files/README.md.template +63 -17
  10. package/src/init/files/angular.json.template +6 -6
  11. package/src/init/files/contributing-docs/coding-standards.md.template +239 -0
  12. package/src/init/files/contributing-docs/using-fixup-commits.md.template +111 -0
  13. package/src/init/files/package.json.template +7 -3
  14. package/src/init/files/src/app/app.config.ts.template +1 -2
  15. package/src/init/files/src/app/core/auth/auth.guard.ts.template +17 -9
  16. package/src/init/files/src/app/core/firebase/cached-listeners.service.ts.template +5 -4
  17. package/src/init/files/src/app/core/firebase/firebase.mock.service.ts.template +3 -4
  18. package/src/init/files/src/app/core/store/app.store.ts.template +13 -3
  19. package/src/init/files/src/app/core/store/user/user.model.ts.template +1 -1
  20. package/src/init/files/src/app/first-time/early-access/early-access.component.ts.template +2 -2
  21. package/src/init/files/src/app/shared/navbar/navbar.component.html.template +1 -1
  22. package/src/init/files/src/app/shared/navbar/navbar.component.scss.template +5 -5
  23. package/src/init/files/src/env.d.ts.template +31 -0
  24. package/src/init/files/src/environments/environment.prod.ts.template +3 -1
  25. package/src/init/files/src/environments/environment.ts.template +2 -1
  26. package/src/init/files/src/index.html.template +7 -7
  27. package/src/init/files/tsconfig.app.json.template +15 -0
package/README.md CHANGED
@@ -52,4 +52,3 @@ That's it!
52
52
 
53
53
  You can also use `npm version <version>` to update the version before publishing.
54
54
  * Don't forget to also update `src/init/files/package.json.template` so that the latest version of `@tech4good/anguar-schematics` is being used in the dependencies.
55
- * If we are making a major update for a new angular version, we also need to update the version number in `package.json.template`.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@tech4good/angular-schematics",
3
- "version": "18.0.2",
3
+ "version": "18.0.4",
4
4
  "description": "A set of schematics for generating modules, containers, components, and entities",
5
5
  "scripts": {
6
6
  "build": "tsc -p tsconfig.json",
@@ -1,5 +1,5 @@
1
1
  import { inject, effect, WritableSignal } from '@angular/core';
2
- import { signalStore, patchState, withState, withMethods } from '@ngrx/signals';
2
+ import { signalStore, withState, withMethods } from '@ngrx/signals';
3
3
  import { withEntities, removeEntity, updateEntity, setEntity, removeEntities, setEntities } from '@ngrx/signals/entities';
4
4
  import { EntityLoadQuery, EntityStreamQuery, selectEntities, processLoadQueries, withEntitiesAndDBMethods } from 'src/app/core/store/app.store';
5
5
  import { QueryParams, QueryOptions, AnyEntity } from 'src/app/core/store/app.model';
@@ -56,7 +56,7 @@ function addInserts(options) {
56
56
  ], [
57
57
  `import { ${classifiedName}MockDB, ${allcapsName}_DB } from '${fbToEntityMockPath}';`,
58
58
  ` '${camelizedName}s': inject(${classifiedName}MockDB),`,
59
- ` patchState(this.DB['${camelizedName}s'], setAllEntities(${allcapsName}_DB, { selectId }));`
59
+ ` this.DB['${camelizedName}s'].init(${allcapsName}_DB);`
60
60
  ]);
61
61
  context.logger.info(`about to start committing`);
62
62
  // For each of the files and corresponding set of changes, commit to the tree
@@ -1 +1 @@
1
- {"version":3,"file":"index.js","sourceRoot":"","sources":["index.ts"],"names":[],"mappings":";;;;;;;;;;;;AAAA,2DAIoC;AAEpC,+DAA0E;AAC1E,yEAA4E;AAC5E,uEAAmE;AACnE,qEAAuF;AACvF,+CAA+C;AAE/C,iEAAyE;AAEzE,SAAS,UAAU,CAAC,OAAY;IAC9B,OAAO,CAAC,IAAU,EAAE,OAAyB,EAAE,EAAE;QAE/C,MAAM,cAAc,GAAG,cAAO,CAAC,QAAQ,CAAC,OAAO,CAAC,IAAI,CAAC,CAAC;QACtD,MAAM,aAAa,GAAG,cAAO,CAAC,QAAQ,CAAC,OAAO,CAAC,IAAI,CAAC,CAAC;QACrD,MAAM,cAAc,GAAG,cAAO,CAAC,SAAS,CAAC,OAAO,CAAC,IAAI,CAAC,CAAC;QACvD,MAAM,WAAW,GAAG,cAAO,CAAC,QAAQ,CAAC,OAAO,CAAC,IAAI,CAAC,CAAC,WAAW,EAAE,CAAC;QACjE,OAAO,CAAC,MAAM,CAAC,IAAI,CAAC,UAAU,cAAc,KAAK,aAAa,EAAE,CAAC,CAAC;QAElE,uBAAuB;QACvB,MAAM,YAAY,GAAG,mCAAmC,CAAC;QACzD,MAAM,YAAY,GAAG,IAAA,gCAAa,EAAC,IAAI,EAAE,YAAY,CAAC,CAAC;QACvD,OAAO,CAAC,MAAM,CAAC,IAAI,CAAC,iBAAiB,YAAY,EAAE,CAAC,CAAC;QAErD,MAAM,eAAe,GACnB,IAAI,OAAO,CAAC,IAAI,GAAG;YACnB,cAAc,GAAG,GAAG;YACpB,cAAc,GAAG,QAAQ,CAAC;QAC5B,OAAO,CAAC,MAAM,CAAC,IAAI,CAAC,oBAAoB,eAAe,EAAE,CAAC,CAAC;QAC3D,MAAM,oBAAoB,GAAG,IAAA,+BAAiB,EAAC,YAAY,EAAE,eAAe,CAAC,CAAC;QAC9E,OAAO,CAAC,MAAM,CAAC,IAAI,CAAC,oBAAoB,oBAAoB,EAAE,CAAC,CAAC;QAEhE,IAAI,uBAAuB,GAAG,IAAA,+BAAY,EACxC,YAAY,EACZ,YAAY,EACZ;YACE,kBAAkB;YAClB,yBAAyB;SAC1B,EACD;YACE,YAAY,cAAc,YAAY,oBAAoB,IAAI;YAC9D,KAAK,cAAc,IAAI;SACxB,CACF,CAAC;QAEF,mCAAmC;QACnC,MAAM,UAAU,GAAG,kDAAkD,CAAC;QACtE,MAAM,UAAU,GAAG,IAAA,gCAAa,EAAC,IAAI,EAAE,UAAU,CAAC,CAAC;QAEnD,MAAM,cAAc,GAClB,IAAI,OAAO,CAAC,IAAI,GAAG;YACnB,cAAc,GAAG,GAAG;YACpB,cAAc,GAAG,OAAO,CAAC;QAC3B,MAAM,kBAAkB,GAAG,IAAA,+BAAiB,EAAC,UAAU,EAAE,cAAc,CAAC,CAAC;QACzE,OAAO,CAAC,MAAM,CAAC,IAAI,CAAC,eAAe,UAAU,EAAE,CAAC,CAAC;QAEjD,IAAI,qBAAqB,GAAG,IAAA,+BAAY,EACtC,UAAU,EACV,UAAU,EACV;YACE,yBAAyB;YACzB,iBAAiB;YACjB,uBAAuB;SACxB,EACD;YACE,YAAY,cAAc,WAAW,WAAW,eAAe,kBAAkB,IAAI;YACrF,QAAQ,aAAa,cAAc,cAAc,UAAU;YAC3D,2BAA2B,aAAa,uBAAuB,WAAW,uBAAuB;SAClG,CACF,CAAC;QAEF,OAAO,CAAC,MAAM,CAAC,IAAI,CAAC,2BAA2B,CAAC,CAAC;QACjD,6EAA6E;QAC7E;YACE,CAAC,YAAY,EAAE,uBAAuB,CAAC;YACvC,CAAC,UAAU,EAAE,qBAAqB,CAAC;SACpC,CAAC,GAAG,CAAC,CAAC,CAAC,QAAQ,EAAE,aAAa,CAAqB,EAAE,EAAE;YAEtD,MAAM,mBAAmB,GAAG,IAAI,CAAC,WAAW,CAAC,QAAQ,CAAC,CAAC;YACvD,KAAK,MAAM,MAAM,IAAI,aAAa,EAAE;gBAClC,IAAI,MAAM,YAAY,qBAAY,EAAE;oBAClC,mBAAmB,CAAC,UAAU,CAAC,MAAM,CAAC,GAAG,EAAE,MAAM,CAAC,KAAK,CAAC,CAAC;iBAC1D;aACF;YACD,IAAI,CAAC,YAAY,CAAC,mBAAmB,CAAC,CAAC;QACzC,CAAC,CAAC,CAAC;QAEH,OAAO,IAAI,CAAC;IACd,CAAC,CAAA;AACH,CAAC;AAED,SAAgB,MAAM,CAAC,OAAY;IACjC,OAAO,CAAO,IAAU,EAAE,OAAyB,EAAE,EAAE;QAErD,6FAA6F;QAC7F,IAAI,CAAC,OAAO,CAAC,WAAW,EAAE;YACxB,OAAO,CAAC,MAAM,CAAC,IAAI,CAAC,yEAAyE,CAAC,CAAC;YAC/F,OAAO,IAAA,iBAAI,GAAE,CAAC;SACf;QAED,MAAM,SAAS,GAAG,MAAM,IAAA,wBAAY,EAAC,IAAI,CAAC,CAAC;QAC3C,MAAM,OAAO,GAAG,SAAS,CAAC,QAAQ,CAAC,GAAG,CAAC,OAAO,CAAC,OAAiB,CAAC,CAAC;QAElE,IAAI,CAAC,OAAO,EAAE;YACZ,MAAM,IAAI,gCAAmB,CAAC,YAAY,OAAO,CAAC,OAAO,mBAAmB,CAAC,CAAC;SAC/E;QAED,IAAI,OAAO,CAAC,IAAI,KAAK,SAAS,EAAE;YAC9B,OAAO,CAAC,IAAI,GAAG,IAAA,4BAAgB,EAAC,OAAO,CAAC,CAAC;SAC1C;QAED,MAAM,UAAU,GAAG,IAAA,sBAAS,EAAC,OAAO,CAAC,IAAc,EAAE,OAAO,CAAC,IAAI,CAAC,CAAC;QACnE,OAAO,CAAC,IAAI,GAAG,UAAU,CAAC,IAAI,CAAC;QAC/B,OAAO,CAAC,IAAI,GAAG,UAAU,CAAC,IAAI,CAAC;QAE/B,MAAM,cAAc,GAAG,IAAA,kBAAK,EAAC,IAAA,gBAAG,EAAC,SAAS,CAAC,EAAE;YAC3C,IAAA,2BAAc,kCACT,cAAO,GACP,OAAO,EACV;YACF,IAAA,iBAAI,EAAC,UAAU,CAAC,IAAI,CAAC;SACtB,CAAC,CAAC;QAEH,OAAO,IAAA,kBAAK,EAAC;YACX,UAAU,CAAC,OAAO,CAAC;YACnB,IAAA,sBAAS,EAAC,cAAc,CAAC;SAC1B,CAAC,CAAC;IACL,CAAC,CAAA,CAAC;AACJ,CAAC;AArCD,wBAqCC"}
1
+ {"version":3,"file":"index.js","sourceRoot":"","sources":["index.ts"],"names":[],"mappings":";;;;;;;;;;;;AAAA,2DAIoC;AAEpC,+DAA0E;AAC1E,yEAA4E;AAC5E,uEAAmE;AACnE,qEAAuF;AACvF,+CAA+C;AAE/C,iEAAyE;AAEzE,SAAS,UAAU,CAAC,OAAY;IAC9B,OAAO,CAAC,IAAU,EAAE,OAAyB,EAAE,EAAE;QAE/C,MAAM,cAAc,GAAG,cAAO,CAAC,QAAQ,CAAC,OAAO,CAAC,IAAI,CAAC,CAAC;QACtD,MAAM,aAAa,GAAG,cAAO,CAAC,QAAQ,CAAC,OAAO,CAAC,IAAI,CAAC,CAAC;QACrD,MAAM,cAAc,GAAG,cAAO,CAAC,SAAS,CAAC,OAAO,CAAC,IAAI,CAAC,CAAC;QACvD,MAAM,WAAW,GAAG,cAAO,CAAC,QAAQ,CAAC,OAAO,CAAC,IAAI,CAAC,CAAC,WAAW,EAAE,CAAC;QACjE,OAAO,CAAC,MAAM,CAAC,IAAI,CAAC,UAAU,cAAc,KAAK,aAAa,EAAE,CAAC,CAAC;QAElE,uBAAuB;QACvB,MAAM,YAAY,GAAG,mCAAmC,CAAC;QACzD,MAAM,YAAY,GAAG,IAAA,gCAAa,EAAC,IAAI,EAAE,YAAY,CAAC,CAAC;QACvD,OAAO,CAAC,MAAM,CAAC,IAAI,CAAC,iBAAiB,YAAY,EAAE,CAAC,CAAC;QAErD,MAAM,eAAe,GACnB,IAAI,OAAO,CAAC,IAAI,GAAG;YACnB,cAAc,GAAG,GAAG;YACpB,cAAc,GAAG,QAAQ,CAAC;QAC5B,OAAO,CAAC,MAAM,CAAC,IAAI,CAAC,oBAAoB,eAAe,EAAE,CAAC,CAAC;QAC3D,MAAM,oBAAoB,GAAG,IAAA,+BAAiB,EAAC,YAAY,EAAE,eAAe,CAAC,CAAC;QAC9E,OAAO,CAAC,MAAM,CAAC,IAAI,CAAC,oBAAoB,oBAAoB,EAAE,CAAC,CAAC;QAEhE,IAAI,uBAAuB,GAAG,IAAA,+BAAY,EACxC,YAAY,EACZ,YAAY,EACZ;YACE,kBAAkB;YAClB,yBAAyB;SAC1B,EACD;YACE,YAAY,cAAc,YAAY,oBAAoB,IAAI;YAC9D,KAAK,cAAc,IAAI;SACxB,CACF,CAAC;QAEF,mCAAmC;QACnC,MAAM,UAAU,GAAG,kDAAkD,CAAC;QACtE,MAAM,UAAU,GAAG,IAAA,gCAAa,EAAC,IAAI,EAAE,UAAU,CAAC,CAAC;QAEnD,MAAM,cAAc,GAClB,IAAI,OAAO,CAAC,IAAI,GAAG;YACnB,cAAc,GAAG,GAAG;YACpB,cAAc,GAAG,OAAO,CAAC;QAC3B,MAAM,kBAAkB,GAAG,IAAA,+BAAiB,EAAC,UAAU,EAAE,cAAc,CAAC,CAAC;QACzE,OAAO,CAAC,MAAM,CAAC,IAAI,CAAC,eAAe,UAAU,EAAE,CAAC,CAAC;QAEjD,IAAI,qBAAqB,GAAG,IAAA,+BAAY,EACtC,UAAU,EACV,UAAU,EACV;YACE,yBAAyB;YACzB,iBAAiB;YACjB,uBAAuB;SACxB,EACD;YACE,YAAY,cAAc,WAAW,WAAW,eAAe,kBAAkB,IAAI;YACrF,QAAQ,aAAa,cAAc,cAAc,UAAU;YAC3D,gBAAgB,aAAa,YAAY,WAAW,OAAO;SAC5D,CACF,CAAC;QAEF,OAAO,CAAC,MAAM,CAAC,IAAI,CAAC,2BAA2B,CAAC,CAAC;QACjD,6EAA6E;QAC7E;YACE,CAAC,YAAY,EAAE,uBAAuB,CAAC;YACvC,CAAC,UAAU,EAAE,qBAAqB,CAAC;SACpC,CAAC,GAAG,CAAC,CAAC,CAAC,QAAQ,EAAE,aAAa,CAAqB,EAAE,EAAE;YAEtD,MAAM,mBAAmB,GAAG,IAAI,CAAC,WAAW,CAAC,QAAQ,CAAC,CAAC;YACvD,KAAK,MAAM,MAAM,IAAI,aAAa,EAAE;gBAClC,IAAI,MAAM,YAAY,qBAAY,EAAE;oBAClC,mBAAmB,CAAC,UAAU,CAAC,MAAM,CAAC,GAAG,EAAE,MAAM,CAAC,KAAK,CAAC,CAAC;iBAC1D;aACF;YACD,IAAI,CAAC,YAAY,CAAC,mBAAmB,CAAC,CAAC;QACzC,CAAC,CAAC,CAAC;QAEH,OAAO,IAAI,CAAC;IACd,CAAC,CAAA;AACH,CAAC;AAED,SAAgB,MAAM,CAAC,OAAY;IACjC,OAAO,CAAO,IAAU,EAAE,OAAyB,EAAE,EAAE;QAErD,6FAA6F;QAC7F,IAAI,CAAC,OAAO,CAAC,WAAW,EAAE;YACxB,OAAO,CAAC,MAAM,CAAC,IAAI,CAAC,yEAAyE,CAAC,CAAC;YAC/F,OAAO,IAAA,iBAAI,GAAE,CAAC;SACf;QAED,MAAM,SAAS,GAAG,MAAM,IAAA,wBAAY,EAAC,IAAI,CAAC,CAAC;QAC3C,MAAM,OAAO,GAAG,SAAS,CAAC,QAAQ,CAAC,GAAG,CAAC,OAAO,CAAC,OAAiB,CAAC,CAAC;QAElE,IAAI,CAAC,OAAO,EAAE;YACZ,MAAM,IAAI,gCAAmB,CAAC,YAAY,OAAO,CAAC,OAAO,mBAAmB,CAAC,CAAC;SAC/E;QAED,IAAI,OAAO,CAAC,IAAI,KAAK,SAAS,EAAE;YAC9B,OAAO,CAAC,IAAI,GAAG,IAAA,4BAAgB,EAAC,OAAO,CAAC,CAAC;SAC1C;QAED,MAAM,UAAU,GAAG,IAAA,sBAAS,EAAC,OAAO,CAAC,IAAc,EAAE,OAAO,CAAC,IAAI,CAAC,CAAC;QACnE,OAAO,CAAC,IAAI,GAAG,UAAU,CAAC,IAAI,CAAC;QAC/B,OAAO,CAAC,IAAI,GAAG,UAAU,CAAC,IAAI,CAAC;QAE/B,MAAM,cAAc,GAAG,IAAA,kBAAK,EAAC,IAAA,gBAAG,EAAC,SAAS,CAAC,EAAE;YAC3C,IAAA,2BAAc,kCACT,cAAO,GACP,OAAO,EACV;YACF,IAAA,iBAAI,EAAC,UAAU,CAAC,IAAI,CAAC;SACtB,CAAC,CAAC;QAEH,OAAO,IAAA,kBAAK,EAAC;YACX,UAAU,CAAC,OAAO,CAAC;YACnB,IAAA,sBAAS,EAAC,cAAc,CAAC;SAC1B,CAAC,CAAC;IACL,CAAC,CAAA,CAAC;AACJ,CAAC;AArCD,wBAqCC"}
@@ -52,3 +52,6 @@ Thumbs.db
52
52
  .firebase
53
53
  *-debug.log
54
54
  .runtimeconfig.json
55
+
56
+ # .env
57
+ .env
@@ -0,0 +1,51 @@
1
+ # Contributor Covenant Code of Conduct
2
+
3
+ ## Our Pledge
4
+
5
+ In the interest of fostering a safe and welcoming environment, we as the Tech4Good team pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity, gender expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
6
+
7
+ ## Our Standards
8
+
9
+ Examples of behavior that contributes to creating a positive environment include:
10
+
11
+ * Use welcoming and inclusive language
12
+ * Respect each other
13
+ * Provide and gracefully accept constructive criticism
14
+ * Show empathy towards other community members
15
+
16
+ Examples of unacceptable behavior by participants include:
17
+
18
+ * Trolling, insulting/derogatory comments, and personal or political attacks
19
+ * Public or private harassment
20
+ * Publishing others' private information, such as a physical or electronic address, without explicit permission
21
+ * The use of sexualized language or imagery
22
+ * Unwelcome sexual attention or advances
23
+ * Other conduct which could reasonably be considered inappropriate in a professional setting
24
+
25
+ ## Our Responsibilities
26
+
27
+ The Tech4Good team is responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
28
+
29
+ The Tech4Good team has the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned with this Code of Conduct, and to ban temporarily or permanently any contributor for behaviors they deem inappropriate, threatening, offensive, or harmful.
30
+
31
+ ## Scope
32
+
33
+ This Code of Conduct applies to all Tech4Good communication channels — online or in person — and it also applies when an individual is representing the project or its community in public spaces. Examples of representing a project or community include using an official project email address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
34
+
35
+ ## Enforcement
36
+
37
+ Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the Tech4Good team at tech4good@ucsc.edu. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The Tech4Good team will maintain confidentiality with regard to the reporter of an incident. Enforcement may result in an indefinite ban from all official Tech4Good communication channels, or other actions as deemed appropriate by the Tech4Good team.
38
+
39
+ Tech4Good maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
40
+
41
+ ### Appeal
42
+
43
+ If you are banned, you may contest the decision. To do so, email tech4good@ucsc.edu with the subject line "Repeal Ban for {{your name here}}" and body with the responses to the following:
44
+
45
+ * Why do you believe you did not violate the Code of Conduct?
46
+ * Were other factors involved in this situation that the leadership team may have been unaware of?
47
+ * Why do you wish to be a part of the Tech4Good community?
48
+
49
+ ## Attribution
50
+
51
+ This Code of Conduct is from [Angular's Code of Conduct](https://github.com/angular/angular/blob/main/CODE_OF_CONDUCT.md), which is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
@@ -0,0 +1,298 @@
1
+ # Contributing
2
+
3
+ Welcome! We’re excited to have you here and appreciate your interest in contributing to our project. As a contributor, here are the guidelines we would like you to follow:
4
+
5
+ - [Code of Conduct](#coc)
6
+ - [Development Setup](#setup)
7
+ - [Submission Guidelines](#submit)
8
+ - [Coding Rules](#rules)
9
+ - [Commit Message Format](#commit)
10
+
11
+ ## <a name="coc"></a> Code of Conduct
12
+
13
+ Help us keep <%= classify(project) %> open and inclusive. Please read and follow our [Code of Conduct](/CODE_OF_CONDUCT.md).
14
+
15
+ ## <a name="setup"></a> Setup and Development
16
+
17
+ ### <a name="prereqs"></a> Prerequisites
18
+
19
+ Before you can build and run <%= classify(project) %>, you must install and configure the following on your development machine:
20
+
21
+ * [Git](https://git-scm.com/) and/or the [**GitHub app**](https://desktop.github.com/) (for Mac and
22
+ Windows);
23
+ [GitHub's Guide to Installing Git](https://help.github.com/articles/set-up-git) is a good source
24
+ of information.
25
+
26
+ * [Node.js](https://nodejs.org), (version specified in [`.nvmrc`](../.nvmrc)) which is used to run a
27
+ development web server, run tests, and generate distributable files.
28
+ `.nvmrc` is read by [nvm](https://github.com/nvm-sh/nvm) commands like `nvm install` and `nvm use`.
29
+
30
+ ### <a name="sources"></a> Getting the Sources
31
+
32
+ Clone the Angular repository:
33
+
34
+ 1. Login to your GitHub account or create one by following the instructions given
35
+ [here](https://github.com/signup/free).
36
+ 2. Clone the <%= classify(project) %> repository
37
+
38
+ ```
39
+ # Clone the GitHub repository:
40
+ git clone git@github.com:tech4good-lab/<%= dasherize(project) %>.git
41
+
42
+ # Go to the directory:
43
+ cd <%= dasherize(project) %>
44
+ ```
45
+
46
+ ### <a name="npm"></a> Installing NPM Modules
47
+
48
+ Next, install the JavaScript modules needed to build and test <%= classify(project) %>:
49
+
50
+ ```shell
51
+ # Install the Angular CLI globally
52
+ npm install -g @angular/cli
53
+
54
+ # Install project dependencies (package.json)
55
+ npm install
56
+ ```
57
+
58
+ ### <a name="building"></a> Running the project locally
59
+
60
+ ```shell
61
+ # Serve the project locally
62
+ ng serve
63
+ ```
64
+
65
+ Once you've served the project, the application will be accessible at `http://localhost:4200/`.
66
+
67
+ ### <a name="testing-the-application"></a> Testing the Application
68
+
69
+ Currently, we have not incorporated testing into our process yet >.< However, we intend to add testing in the future.
70
+
71
+ ## <a name="submit"></a> Submission Guidelines
72
+
73
+ ### <a name="submit-issue"></a> Submitting an Issue
74
+
75
+ Before you submit an issue, please search the issue tracker. An issue for your problem might already exist, and the discussion might inform you of workarounds readily available. We cannot promise that we will be able to resolve issues quickly.
76
+
77
+ Given our limited capacity, we will likely only be able to address bugs that can be reproduced. Please provide instructions for how to reproduce it and a recording of the bug. If we don't hear back from you, we may close issues that do not have enough information to be reproduced.
78
+
79
+ You can file new issues by selecting from our [new issue templates](TBD) and filling out the issue template.
80
+
81
+ ### <a name="submit-pr"></a> Submitting a Pull Request (PR)
82
+
83
+ Before you submit your Pull Request (PR), consider the following guidelines:
84
+
85
+ 1. Search [GitHub](TBD) for an open or closed PR that relates to your submission. You don't want to duplicate existing efforts.
86
+
87
+ 2. Ensure that an issue describes the problem you're fixing or documents the design for the feature you'd like to add.
88
+
89
+ 3. In your forked repository, make your changes in a new git branch:
90
+
91
+ ```shell
92
+ git checkout -b my-fix-branch develop
93
+ ```
94
+
95
+ 4. Create your patch.
96
+
97
+ 5. Follow our [Coding Rules](#rules).
98
+
99
+ 6. Commit your changes using a descriptive commit message that follows our [commit message conventions](#commit). Adherence to these conventions is necessary because release notes are automatically generated from these messages.
100
+
101
+ ```shell
102
+ git commit --all
103
+ ```
104
+ Note: The optional commit `--all` command line option will automatically "add" and "rm" edited files.
105
+
106
+ 7. Push your branch to GitHub:
107
+
108
+ ```shell
109
+ git push origin my-fix-branch
110
+ ```
111
+
112
+ 8. In GitHub, send a pull request to `<%= dasherize(project) %>:develop`.
113
+
114
+ ### <a name="review-pr"></a> Reviewing a Pull Request
115
+
116
+ The team reserves the right not to accept pull requests from community members who haven't been good citizens of the community. Such behavior includes not following the [code of conduct](/CODE_OF_CONDUCT.md) and applies within or outside of our managed channels.
117
+
118
+ #### Addressing review feedback
119
+
120
+ If we ask for changes via code reviews, then:
121
+
122
+ 1. Make the required updates to the code.
123
+
124
+ 2. Create a fixup commit and push to your GitHub repository (this will update your Pull Request):
125
+
126
+ ```shell
127
+ git commit --all --fixup HEAD
128
+ git push
129
+ ```
130
+
131
+ For more info on working with fixup commits, see [here](./contributing-docs/using-fixup-commits.md).
132
+
133
+ That's it! Thank you for your contribution!
134
+
135
+ ##### <a name="update-commit"></a> Updating the commit message
136
+
137
+ A reviewer might often suggest changes to a commit message (for example, to add more context for a change or adhere to our [commit message guidelines](#commit)). In order to update the commit message of the last commit on your branch:
138
+
139
+ 1. Check out your branch:
140
+
141
+ ```shell
142
+ git checkout my-fix-branch
143
+ ```
144
+
145
+ 2. Amend the last commit and modify the commit message:
146
+
147
+ ```shell
148
+ git commit --amend
149
+ ```
150
+
151
+ 3. Push to your GitHub repository:
152
+
153
+ ```shell
154
+ git push --force-with-lease
155
+ ```
156
+
157
+ > NOTE:<br />
158
+ > If you need to update the commit message of an earlier commit, you can use `git rebase` in interactive mode. See the [git docs](https://git-scm.com/docs/git-rebase#_interactive_mode) for more details.
159
+
160
+ #### <a name="pr-merge"></a> After your pull request is merged
161
+
162
+ After your pull request is merged, you can safely delete your branch and pull the changes from the `develop` (upstream) repository:
163
+
164
+ * Delete the remote branch on GitHub either through the GitHub web UI or your local shell as follows:
165
+
166
+ ```shell
167
+ git push origin --delete my-fix-branch
168
+ ```
169
+
170
+ * Check out the `develop` branch:
171
+
172
+ ```shell
173
+ git checkout develop -f
174
+ ```
175
+
176
+ * Delete the local branch:
177
+
178
+ ```shell
179
+ git branch -D my-fix-branch
180
+ ```
181
+
182
+ * Update your local `develop` with the latest upstream version:
183
+
184
+ ```shell
185
+ git pull --ff upstream develop
186
+ ```
187
+
188
+ ## <a name="rules"></a> Coding Rules
189
+
190
+ To ensure consistency throughout the source code, keep these rules in mind as you are working:
191
+
192
+ <!-- * All features or bug fixes **must be tested** by one or more specs (unit-tests).-->
193
+ * All public API methods **must be documented**.
194
+ * We follow [Google's JavaScript Style Guide](https://google.github.io/styleguide/jsguide.html), but wrap all code at **100 characters**.
195
+ * More details on our coding standards can be found in our [Coding Standards](contributing-docs/coding-standards.md) document. Please follow these rules to maintain code quality.
196
+
197
+ ## <a name="commit"></a> Commit Message Format
198
+
199
+ We have very precise rules over how our Git commit messages must be formatted using [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0). This format leads to **easier-to-read commit history**.
200
+
201
+ Each commit message consists of a **header**, a **body**, and a **footer**.
202
+
203
+ ```
204
+ <header>
205
+ <BLANK LINE>
206
+ <body>
207
+ <BLANK LINE>
208
+ <footer>
209
+ ```
210
+
211
+ The `header` is mandatory and must conform to the [Commit Message Header](#commit-header) format.
212
+
213
+ The `body` is mandatory for all commits except for those of type "docs". When the body is present, it must be at least 20 characters long and must conform to the [Commit Message Body](#commit-body) format.
214
+
215
+ The `footer` is optional. The [Commit Message Footer](#commit-footer) format describes what the footer is used for and the structure it must have.
216
+
217
+ #### <a name="commit-header"></a>Commit Message Header
218
+
219
+ ```
220
+ <type>(<scope>): <short summary>
221
+ │ │ │
222
+ │ │ └─⫸ Summary in present tense. Not capitalized. No period at the end.
223
+ │ │
224
+ │ └─⫸ Commit Scope:public|admin|core|main|first-time|shared|...
225
+ │
226
+ └─⫸ Commit Type: build|ci|docs|feat|fix|perf|refactor|test
227
+ ```
228
+
229
+ The `<type>` and `<summary>` fields are mandatory; the `(<scope>)` field is optional.
230
+
231
+ ##### Type
232
+
233
+ Will most commonly be either `feat` or `fix`, but can be drawn from any of the below following angular practices:
234
+
235
+ - **build**: Changes that affect the build system or external dependencies
236
+ - **ci**: Changes to our CI configuration files and scripts
237
+ - **docs**: Documentation-only changes
238
+ - **feat**: A new feature
239
+ - **fix**: A bug fix
240
+ - **perf**: A code change that improves performance
241
+ - **refactor**: A code change that neither fixes a bug nor adds a feature
242
+ - **style**: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
243
+ - **test**: Adding missing tests or correcting existing tests
244
+
245
+ ##### Scope
246
+
247
+ The scope will most commonly corresponds to one of the folders directly underneath app (i.e. what used to correspond to a module before standalone components). For example:
248
+
249
+ - **public**
250
+ - **admin**
251
+ - **core**
252
+ - **main**
253
+ - **first-time**
254
+ - **shared**
255
+
256
+ There are currently a few exceptions to this rule:
257
+
258
+ - **packaging**: used for changes that change the npm package layout in all of our packages, e.g. public path changes, package.json changes done to all packages, d.ts file/format changes, changes to bundles, etc.
259
+ - **changelog** for updating the release notes in CHANGELOG.md
260
+ - none/empty string: useful for style, test and refactor changes that are done across all packages (e.g. style: add missing semicolons)
261
+
262
+ ##### Summary
263
+
264
+ The summary contains a succinct description of the change:
265
+
266
+ * use the imperative, present tense: "change" not "changed" nor "changes"
267
+ * don't capitalize the first letter
268
+ * no dot (.) at the end
269
+
270
+ #### <a name="commit-body"></a>Commit Message Body
271
+
272
+ Just as in the summary, use the imperative, present tense: "fix" not "fixed" nor "fixes".
273
+
274
+ Explain the motivation for the change in the commit message body. This commit message should explain _why_ you are making this change. You can include a comparison of the previous behavior with the new behavior in order to illustrate the impact of the change.
275
+
276
+ #### <a name="commit-footer"></a>Commit Message Footer
277
+
278
+ The footer can contain information about breaking changes and is also the place to reference GitHub issues and other PRs that this commit closes or is related to. For example:
279
+
280
+ ```
281
+ BREAKING CHANGE: <breaking change summary>
282
+ <BLANK LINE>
283
+ <breaking change description + migration instructions>
284
+ <BLANK LINE>
285
+ <BLANK LINE>
286
+ Fix #<issue number>, Close #<pr number>
287
+ ```
288
+
289
+ Breaking Change section should start with the phrase `BREAKING CHANGE: ` followed by a summary of the breaking change, a blank line, and a detailed description of the breaking change that also includes migration instructions.
290
+
291
+ ### Revert commits
292
+
293
+ If the commit reverts a previous commit, it should begin with `revert: `, followed by the header of the reverted commit.
294
+
295
+ The content of the commit message body should contain:
296
+
297
+ - information about the SHA of the commit being reverted in the following format: `This reverts commit <SHA>`,
298
+ - a clear description of the reason for reverting the commit message.
@@ -1,27 +1,73 @@
1
- # <%= classify(project) %>
1
+ <h1 align="center"><%= classify(project) %></h1>
2
+ <p align="center">
3
+ <img src="/public/images/logo.svg" alt="logo" width="120px" height="120px"/>
4
+ <br>
5
+ <em><%= classify(project) %> provides [short value statement]</em>
6
+ <br>
7
+ </p>
8
+ <p align="center">
9
+ <a><strong><%= classify(project)</strong> [Link TBD]</a> by <a><strong>[the creators]</strong></a>
10
+ </p>
2
11
 
3
- This project was initialized by using [Tech4Good's Angular Schematics](https://github.com/tech4good-lab/angular-schematics) after a base project repository was generated with [Angular CLI](https://github.com/angular/angular-cli).
12
+ <p align="center">
13
+ <a href="CONTRIBUTING.md">Contributing Guidelines</a>
14
+ </p>
4
15
 
5
- ## Development server
16
+ <hr>
6
17
 
7
- Run `ng serve` for a dev server. Navigate to `http://localhost:4200/`. The app will automatically reload if you change any of the source files.
8
- Run `ng serve --configuration production` to run a prod server locally. Navigate to `http://localhost:4200/`. The app will automatically reload if you change any of the source files.
18
+ ## Overview
9
19
 
10
- ## Build
20
+ [Project description and novelty]
11
21
 
12
- Run `ng build` to build the project. The build artifacts will be stored in the `dist/` directory.
13
- Run `firebase deploy` to deploy to production and `firebase deploy -P dev` to deploy to dev
22
+ Our platform uses the Angular framework along with Angular Material, RxJS, Typescript, and Sass. We use NgRx's Signal Store for frontend data management, Firebase for the backend, and dotenvx for environment variables.
14
23
 
15
- ## Code generation
24
+ <div align="center">
25
+ <img src="/public/favicon.ico" alt="Angular" width="40" height="40">
26
+ <img src="/public/images/angular-material-icon.png" alt="Angular Material" width="40" height="40">
27
+ <img src="/public/images/rxjs.png" alt="RxJS" width="40" height="40">
28
+ <img src="/public/images/typescript-icon.png" alt="TypeScript" width="40" height="40">
29
+ <img src="/public/images/sass.svg" alt="Sass" width="40" height="40">
30
+ <img src="/public/images/ngrx-icon.svg" alt="NgRx" width="40" height="40">
31
+ <img src="/public/images/firebase-icon.png" alt="Firebase" width="40" height="40">
32
+ </div>
16
33
 
17
- * Run `ng g component component-name` inside the folder where you want a new component to generate it.
18
- * Run `ng g entity entity-name` inside `src/app/core/store` to generate a new entity and add appropriate lines in app.model.ts and firebase.mock.service.ts.
19
- * We ran `ng g init` on a newly generated Angular V18 repo to set up the core infrastructure. This should not be run again as it will rewrite several app-wide files like package.json, app.routes.ts, app.model.ts, firebase.mock.service.ts, etc. where you will have likely added new code since creation of the repository.
34
+ ## Changelog
20
35
 
36
+ For detailed information on changes and updates, please refer to our [Changelog](CHANGELOG.md).
21
37
 
22
- ## Version number
38
+ ## Contributing
23
39
 
24
- We use the syntax `MAJOR.MINOR.PATCH` for versioning, where
25
- * `MAJOR` contains significant new features or overhauls of the user experience requiring user adaptation, removal of features, or data migration that could result in data loss
26
- * `MINOR` contains performance improvements, non-disruptive ui enhancements, and new smaller features that enhance the application but don't interfere with existing features
27
- * `PATCH` contains bug fixes, minor usability and performance fixes that don't add new capabilities
40
+ Want to report a bug, contribute some code, or improve the documentation? Excellent! Read through our [Contributing Guidelines](CONTRIBUTING.md) to learn about our submission process, coding rules, and more.
41
+
42
+ ### Found a Bug?
43
+
44
+ If you encounter any bugs, please [submit an issue](/issues/new?assignees=&labels=bug&template=bug_report.md&title=) using our **Bug Report** template on GitHub. Make sure to fill in all the required details, including a minimal reproduction of the bug, to help us address the issue quickly and effectively.
45
+
46
+ ### Missing a Feature?
47
+
48
+ You can *request* a new feature by [submitting an issue](/issues/new?assignees=&labels=enhancement&template=feature_request.md&title=) using our **Feature Request** template on GitHub. If you would like to *implement* a new feature, please open an issue first to discuss the proposal with the community and maintainers before creating a Pull Request.
49
+
50
+ ### Got a Question or Problem?
51
+
52
+ Do not open issues for general support questions. Instead, we recommend using [GitHub Discussions](/discussions) for any support-related questions. GitHub Discussions is a better place for questions because:
53
+ - The community can engage directly, providing faster and more collaborative answers.
54
+ - Questions and answers remain visible, so your inquiry and its resolution can help others in the future.
55
+ - The voting and answer system helps highlight the most helpful responses.
56
+ To save everyone’s time, we will systematically close any issues that are requests for general support and redirect users to GitHub Discussions.
57
+
58
+ ### Code of Conduct
59
+
60
+ Help us keep <%= classify(project) %> open and inclusive. Please read and follow our [Code of Conduct](CODE_OF_CONDUCT.md).
61
+
62
+ ## Community
63
+
64
+ You can connect with us Lab through the following channels:
65
+
66
+ - [Instagram: @tech4good.ucsc](https://www.instagram.com/tech4good.ucsc/)
67
+ - [Email: tech4good@ucsc.edu](mailto:tech4good@ucsc.edu)
68
+
69
+ ## Credit
70
+
71
+ As can be clearly seen, our documents and the processes we aim to work towards are modeled after or directly taken from those of the [Angular team](https://github.com/angular/angular).
72
+
73
+ **Love <%= classify(project) %>? Give our repo a star :star: :arrow_up:.**
@@ -25,7 +25,7 @@
25
25
  "prefix": "app",
26
26
  "architect": {
27
27
  "build": {
28
- "builder": "@angular-devkit/build-angular:application",
28
+ "builder": "@ngx-env/builder:application",
29
29
  "options": {
30
30
  "outputPath": "dist/<%= dasherize(project) %>",
31
31
  "index": "src/index.html",
@@ -40,10 +40,10 @@
40
40
  "tsConfig": "tsconfig.app.json",
41
41
  "inlineStyleLanguage": "scss",
42
42
  "assets": [
43
- {
43
+ {
44
44
  "glob": "**/*",
45
45
  "input": "public"
46
- },
46
+ }
47
47
  ],
48
48
  "styles": [
49
49
  "@angular/material/prebuilt-themes/azure-blue.css",
@@ -87,7 +87,7 @@
87
87
  "defaultConfiguration": "production"
88
88
  },
89
89
  "serve": {
90
- "builder": "@angular-devkit/build-angular:dev-server",
90
+ "builder": "@ngx-env/builder:dev-server",
91
91
  "configurations": {
92
92
  "production": {
93
93
  "buildTarget": "<%= dasherize(project) %>:build:production"
@@ -99,10 +99,10 @@
99
99
  "defaultConfiguration": "development"
100
100
  },
101
101
  "extract-i18n": {
102
- "builder": "@angular-devkit/build-angular:extract-i18n"
102
+ "builder": "@ngx-env/builder:extract-i18n"
103
103
  },
104
104
  "test": {
105
- "builder": "@angular-devkit/build-angular:karma",
105
+ "builder": "@ngx-env/builder:karma",
106
106
  "options": {
107
107
  "polyfills": [
108
108
  "zone.js",
@@ -0,0 +1,239 @@
1
+ # Coding Standards
2
+
3
+ This is currently partially aspirational as we do not have our CI and prettier setup to enforce these yet. But in general, we'd like to follow the Angular coding standards described below.
4
+
5
+ ## Code Style
6
+
7
+ The **[Google JavaScript Style Guide](https://google.github.io/styleguide/jsguide.html)** serves as the foundation for Causeway's coding style, with additional guidelines specific to TypeScript. The team uses `prettier` to automatically format code, and automatic formatting is enforced by CI.
8
+
9
+ ## Code Practices
10
+
11
+ ### Write Useful Comments
12
+
13
+ Comments that explain what a block of code does are helpful; they can provide clarity faster than following through the code itself.
14
+
15
+ However, comments that explain **why** a block of code exists, or why it does something a certain way, are invaluable. The "why" is often difficult, or sometimes impossible, to discern without consulting the original author. When collaborators are in different locations, this can significantly impact productivity.
16
+
17
+ For example, this is a not-very-useful comment:
18
+ ```typescript
19
+ // Set default tabindex.
20
+ if (!attributes['tabindex']) {
21
+ element.setAttribute('tabindex', '-1');
22
+ }
23
+ ```
24
+
25
+ While this is much more useful:
26
+ ```typescript
27
+ // Unless the user specifies otherwise, the calendar should not be a tab stop.
28
+ // This prevents ngAria from overzealously adding a tabindex to anything with an ng-model.
29
+ if (!attributes['tabindex']) {
30
+ element.setAttribute('tabindex', '-1');
31
+ }
32
+ ```
33
+
34
+ In TypeScript code, use JsDoc-style comments for descriptions (on classes, members, etc.) and `//` style comments for everything else (explanations, background info, etc.).
35
+
36
+ ### API Design
37
+
38
+ #### Boolean Arguments
39
+
40
+ Generally avoid adding boolean arguments to a method in cases where that argument means "do something extra." In these cases, prefer breaking the behavior up into different functions.
41
+
42
+ ```typescript
43
+ // AVOID
44
+ function getTargetElement(createIfNotFound = false) {
45
+ // ...
46
+ }
47
+ ```
48
+
49
+ ```typescript
50
+ // PREFER
51
+ function getExistingTargetElement() {
52
+ // ...
53
+ }
54
+
55
+ function createTargetElement() {
56
+ // ...
57
+ }
58
+ ```
59
+
60
+ This guideline can be relaxed for performance reasons in core framework code.
61
+
62
+ #### Optional Arguments
63
+
64
+ Use optional function arguments only when they make sense for the API or are required for performance. Do not use optional arguments merely for implementation convenience.
65
+
66
+ ### TypeScript
67
+
68
+ #### Typing
69
+
70
+ Avoid using `any` wherever possible. If you find yourself using `any`, consider whether a generic or `unknown` type might be more appropriate.
71
+
72
+ #### Getters and Setters
73
+
74
+ Getters and setters can introduce openings for side effects, add complexity for code readers, and generate additional code when targeting older browsers.
75
+
76
+ * Only use getters and setters for `@Input` properties or when otherwise required for API compatibility.
77
+ * Avoid long or complex getters and setters. If the logic of an accessor would take more than three lines, introduce a new method to contain the logic.
78
+ * A getter should immediately precede its corresponding setter.
79
+ * Decorators such as `@Input` should be applied to the getter and not the setter.
80
+ * Always use a `readonly` property instead of a getter (with no setter) when possible.
81
+
82
+ ```typescript
83
+ /** YES */
84
+ readonly active: boolean;
85
+
86
+ /** NO */
87
+ get active(): boolean {
88
+ // Using a getter solely to make the property read-only.
89
+ return this._active;
90
+ }
91
+ ```
92
+
93
+ #### Iteration
94
+
95
+ Prefer using `for` or `for of` over `Array.prototype.forEach`. The `forEach` API can make debugging harder and may increase overhead due to unnecessary function invocations (though modern browsers typically optimize this well).
96
+
97
+ #### JsDoc Comments
98
+
99
+ All public APIs must have user-facing comments. These are extracted for API documentation and shown in IDEs.
100
+
101
+ Private and internal APIs should have JsDoc when they are not obvious. Ultimately, it is up to the code reviewer to determine what is "obvious," but the rule of thumb is that *most* classes, properties, and methods should have a JsDoc description.
102
+
103
+ Properties should have a concise description of what the property means:
104
+ ```typescript
105
+ /** The label position relative to the checkbox. Defaults to 'after'. */
106
+ @Input() labelPosition: 'before' | 'after' = 'after';
107
+ ```
108
+
109
+ Method blocks should describe what the function does and provide a description for each parameter and the return value:
110
+ ```typescript
111
+ /**
112
+ * Opens a modal dialog containing the given component.
113
+ * @param component Type of the component to load into the dialog.
114
+ * @param config Dialog configuration options.
115
+ * @returns Reference to the newly-opened dialog.
116
+ */
117
+ open<T>(component: ComponentType<T>, config?: MatDialogConfig): MatDialogRef<T> { ... }
118
+ ```
119
+
120
+ Boolean properties and return values should use "Whether..." as opposed to "True if...":
121
+ ```typescript
122
+ /** Whether the button is disabled. */
123
+ disabled: boolean = false;
124
+ ```
125
+
126
+ #### Try-Catch
127
+
128
+ Only use `try-catch` blocks when dealing with genuinely unexpected errors. Don't use `try` to avoid checking for expected error conditions, such as null dereference or out-of-bound array access.
129
+
130
+ Each `try-catch` block **must** include a comment explaining the specific error being caught and why it cannot be prevented.
131
+
132
+ #### Variable Declarations
133
+
134
+ Prefer `const` wherever possible, using `let` only when a value must change. Avoid using `var` unless absolutely necessary.
135
+
136
+ #### `readonly`
137
+
138
+ Use `readonly` members whenever possible to prevent unintended mutations.
139
+
140
+ ### Naming Conventions
141
+
142
+ #### General
143
+
144
+ * Prefer writing out words instead of using abbreviations.
145
+ * Prefer *exact* names over short names (within reason). For example, `labelPosition` is better than `align` because the former more precisely communicates what the property represents.
146
+ * Use `is` and `has` prefixes for boolean properties/methods, except for `@Input()` properties.
147
+ * Name identifiers based on their responsibility. Names should reflect what the code *does*, not how it is used:
148
+
149
+ ```typescript
150
+ /** NO: */
151
+ class DefaultRouteReuseStrategy { }
152
+
153
+ /** YES: */
154
+ class NonStoringRouteReuseStrategy { }
155
+ ```
156
+
157
+ #### Observables
158
+
159
+ Do not suffix observables with `$`.
160
+
161
+ #### Classes
162
+
163
+ * Use PascalCase (UpperCamelCase) for class names.
164
+ * Avoid suffixing class names with `Impl`.
165
+
166
+ #### Interfaces
167
+
168
+ * Do not prefix interfaces with `I`.
169
+ * Avoid suffixing interfaces with `Interface`.
170
+
171
+ #### Functions and Methods
172
+
173
+ Use camelCase (lowerCamelCase) for function and method names.
174
+
175
+ The name of a function should capture the action performed *by* that method rather than describing when the method will be called. For example:
176
+
177
+ ```typescript
178
+ /** AVOID: does not describe what the function does. */
179
+ handleClick() {
180
+ // ...
181
+ }
182
+
183
+ /** PREFER: describes the action performed by the function. */
184
+ activateRipple() {
185
+ // ...
186
+ }
187
+ ```
188
+
189
+ #### Constants and Injection Tokens
190
+
191
+ Use UPPER_SNAKE_CASE for constants and injection tokens.
192
+
193
+ #### Test Classes and Examples
194
+
195
+ Provide test classes and examples with meaningful, descriptive names:
196
+
197
+ ```typescript
198
+ /** PREFER: describes the scenario under test. */
199
+ class FormGroupWithCheckboxAndRadios { /* ... */ }
200
+ class InputWithNgModel { /* ... */ }
201
+
202
+ /** AVOID: does not fully describe the scenario under test. */
203
+ class Comp { /* ... */ }
204
+ class InputComp { /* ... */ }
205
+ ```
206
+
207
+ ### RxJS
208
+
209
+ When importing the `of` function to create an `Observable` from a value, alias the imported function as `observableOf`:
210
+
211
+ ```typescript
212
+ import {of as observableOf} from 'rxjs';
213
+ ```
214
+
215
+ ### Testing
216
+
217
+ #### Test Names
218
+
219
+ Use descriptive names for Jasmine tests. Ideally, test names should read as a sentence, often in the form "it should...".
220
+
221
+ ```typescript
222
+ /** PREFER: describes the scenario under test. */
223
+ describe('Router', () => {
224
+ describe('with the default route reuse strategy', () => {
225
+ it('should not reuse routes upon location change', () => {
226
+ // ...
227
+ });
228
+ });
229
+ });
230
+
231
+ /** AVOID: does not fully describe the scenario under test. */
232
+ describe('Router', () => {
233
+ describe('default strategy', () => {
234
+ it('should work', () => {
235
+ // ...
236
+ });
237
+ });
238
+ });
239
+ ```
@@ -0,0 +1,111 @@
1
+ # Working with fixup commits
2
+
3
+ This document provides information and guidelines for working with fixup commits:
4
+
5
+ - [What are fixup commits](#about-fixup-commits)
6
+ - [Why use fixup commits](#why-fixup-commits)
7
+ - [Creating fixup commits](#create-fixup-commits)
8
+ - [Squashing fixup commits](#squash-fixup-commits)
9
+
10
+ [This blog post](https://thoughtbot.com/blog/autosquashing-git-commits) is also a good resource on
11
+ the subject.
12
+
13
+ ## <a name="about-fixup-commits"></a> What are fixup commits
14
+
15
+ At their core, fixup commits are just regular commits with a special commit message:
16
+ The first line of their commit message starts with "fixup! " (notice the space after "!") followed
17
+ by the first line of the commit message of an earlier commit (it doesn't have to be the immediately
18
+ preceding one).
19
+
20
+ The purpose of a fixup commit is to modify an earlier commit.
21
+ I.e. it allows adding more changes in a new commit, but "marking" them as belonging to an earlier
22
+ commit.
23
+ `Git` provides tools to make it easy to squash fixup commits into the original commit at a later
24
+ time (see [below](#squash-fixup-commits) for details).
25
+
26
+ For example, let's assume you have added the following commits to your branch:
27
+
28
+ ```
29
+ feat: first commit
30
+ fix: second commit
31
+ ```
32
+
33
+ If you want to add more changes to the first commit, you can create a new commit with the commit
34
+ message:
35
+ `fixup! feat: first commit`:
36
+
37
+ ```
38
+ feat: first commit
39
+ fix: second commit
40
+ fixup! feat: first commit
41
+ ```
42
+
43
+ ## <a name="why-fixup-commits"></a> Why use fixup commits
44
+
45
+ So, when are fixup commits useful?
46
+
47
+ During the life of a Pull Request, a reviewer might request changes.
48
+ The Pull Request author can make the requested changes and submit them for another review.
49
+ Normally, these changes should be part of one of the original commits of the Pull Request.
50
+ However, amending an existing commit with the changes makes it difficult for the reviewer to know
51
+ exactly what has changed since the last time they reviewed the Pull Request.
52
+
53
+ Here is where fixup commits come in handy.
54
+ By addressing review feedback in fixup commits, you make it very straight forward for the reviewer
55
+ to see what are the new changes that need to be reviewed and verify that their earlier feedback has
56
+ been addressed.
57
+ This can save a lot of effort, especially on larger Pull Requests (where having to re-review _all_
58
+ the changes is pretty wasteful).
59
+
60
+ When the time comes to merge the Pull Request into the repository, the merge script knows how to
61
+ automatically squash fixup commits with the corresponding regular commits.
62
+
63
+ ## <a name="create-fixup-commits"></a> Creating fixup commits
64
+
65
+ As mentioned [above](#about-fixup-commits), the only thing that differentiates a fixup commit from a
66
+ regular commit is the commit message.
67
+ You can create a fixup commit by specifying an appropriate commit message (
68
+ i.e. `fixup! <original-commit-message-subject>`).
69
+
70
+ In addition, the `git` command-line tool provides an easy way to create a fixup commit
71
+ via [git commit --fixup](https://git-scm.com/docs/git-commit#Documentation/git-commit.txt---fixupltcommitgt):
72
+
73
+ ```sh
74
+ # Create a fixup commit to fix up the last commit on the branch:
75
+ git commit --fixup HEAD ...
76
+
77
+ # Create a fixup commit to fix up commit with SHA <COMMIT_SHA>:
78
+ git commit --fixup <COMMIT_SHA> ...
79
+ ```
80
+
81
+ ## <a name="squash-fixup-commits"></a> Squashing fixup commits
82
+
83
+ As mentioned above, the merge script will automatically squash fixup commits.
84
+ However, sometimes you might want to manually squash a fixup commit.
85
+
86
+ ### Rebasing to squash fixup commits
87
+
88
+ The easiest way to re-order and squash any commit is
89
+ via [rebasing interactively](https://git-scm.com/docs/git-rebase#_interactive_mode). You move a
90
+ commit right after the one you want to squash it into in the rebase TODO list and change the
91
+ corresponding action from `pick` to `fixup`.
92
+
93
+ `Git` can do all these automatically for you if you pass the `--autosquash` option to `git rebase`.
94
+ See the [`git` docs](https://git-scm.com/docs/git-rebase#Documentation/git-rebase.txt---autosquash)
95
+ for more details.
96
+
97
+ ### Additional options
98
+
99
+ You may like to consider some optional configurations:
100
+
101
+ #### Configuring `git` to auto-squash by default
102
+
103
+ By default, `git` will not automatically squash fixup commits when interactively rebasing.
104
+ If you prefer to not have to pass the `--autosquash` option every time, you can change the default
105
+ behavior by setting the `rebase.autoSquash` `git` config option to true.
106
+ See
107
+ the [`git` docs](https://git-scm.com/docs/git-rebase#Documentation/git-rebase.txt-rebaseautoSquash)
108
+ for more details.
109
+
110
+ If you have `rebase.autoSquash` set to true, you can pass the `--no-autosquash` option
111
+ to `git rebase` to override and disable this setting.
@@ -1,6 +1,7 @@
1
1
  {
2
2
  "name": "<%= dasherize(project) %>",
3
3
  "version": "0.0.0",
4
+ "type": "module",
4
5
  "scripts": {
5
6
  "ng": "ng",
6
7
  "start": "ng serve",
@@ -23,11 +24,13 @@
23
24
  "@angular/platform-browser": "^18.0.0",
24
25
  "@angular/platform-browser-dynamic": "^18.0.0",
25
26
  "@angular/router": "^18.0.0",
26
- "@ngrx/signals": "^18.0.0-rc.2",
27
+ "@ngrx/signals": "^18.0.0",
27
28
  "core-js": "^3.37.1",
28
29
  "cross-fetch": "^4.0.0",
29
30
  "crypto-es": "^2.1.0",
31
+ "dotenv": "^16.4.5",
30
32
  "globalthis": "^1.0.4",
33
+ "ngx-env": "^0.1.0",
31
34
  "proxy-polyfill": "^0.3.2",
32
35
  "rxjs": "~7.8.0",
33
36
  "tslib": "^2.3.0",
@@ -42,10 +45,11 @@
42
45
  "@angular-eslint/template-parser": "^18.1.0",
43
46
  "@angular/cli": "^18.0.7",
44
47
  "@angular/compiler-cli": "^18.0.0",
45
- "@tech4good/angular-schematics": "^18.0.2",
48
+ "@ngx-env/builder": "^18.0.1",
49
+ "@tech4good/angular-schematics": "^18.0.4",
46
50
  "@types/estree": "^1.0.0",
47
51
  "@types/jasmine": "~5.1.0",
48
- "@types/node": "^18.18.0",
52
+ "@types/node": "^18.19.47",
49
53
  "@typescript-eslint/eslint-plugin": "6.10.0",
50
54
  "@typescript-eslint/parser": "6.10.0",
51
55
  "eslint-config-google": "^0.14.0",
@@ -1,5 +1,5 @@
1
1
  import { ApplicationConfig, provideZoneChangeDetection } from '@angular/core';
2
- import { provideRouter, withHashLocation, withComponentInputBinding, withPreloading, PreloadAllModules } from '@angular/router';
2
+ import { provideRouter, withComponentInputBinding, withPreloading, PreloadAllModules } from '@angular/router';
3
3
  import { routes } from './app.routes';
4
4
  import { provideAnimationsAsync } from '@angular/platform-browser/animations/async';
5
5
  import { importProvidersFrom } from '@angular/core';
@@ -43,7 +43,6 @@ export const appConfig: ApplicationConfig = {
43
43
  provideZoneChangeDetection({ eventCoalescing: true }),
44
44
  provideRouter(
45
45
  routes,
46
- withHashLocation(),
47
46
  withComponentInputBinding(),
48
47
  withPreloading(PreloadAllModules),
49
48
  ),
@@ -18,8 +18,10 @@ export class AuthGuard {
18
18
  private router: Router,
19
19
  @Inject(DATABASE_SERVICE) private db: DatabaseService,
20
20
  ) {
21
+ // This is only used when we have a signed in user, so we want to filter
22
+ // out the values before the user has been loaded into the store
21
23
  this.user$ = toObservable(this.authStore.user).pipe(
22
- filter((user) => user !== null),
24
+ filter((user) => !!user),
23
25
  );
24
26
  }
25
27
 
@@ -34,13 +36,20 @@ export class AuthGuard {
34
36
  // - Admin users are also handled (so that only admin users can go to admin pages, including pages they would
35
37
  // typically get rerouted from)
36
38
 
37
- // First handle whether users are logged in. If not, go to landing, otherwise go to the hompage
38
- if (!dbUser && (state.url !== '/' && state.url !== '/landing')) {
39
- this.router.navigate(['/'], { queryParams: next.queryParams });
40
- return of(false);
41
- } else if (!dbUser && (state.url === '/' || state.url === '/landing')) {
42
- return of(true);
43
- } else if (dbUser && (state.url === '/' || state.url === '/landing')) {
39
+ // First handle all not logged in cases. If not logged in, users can only go to landing
40
+ if (!dbUser) {
41
+ if (state.url === '/' || state.url === '/landing' || state.url === '/login') {
42
+ return of(true);
43
+ } else {
44
+ this.router.navigate(['/'], { queryParams: next.queryParams });
45
+ return of(false);
46
+ }
47
+ }
48
+
49
+ // AFTER THIS POINT, THE USER MUST BE LOGGED IN (i.e. dbUser exists)
50
+
51
+ // If logged in and trying to access landing, redirect to the homepage
52
+ if (state.url === '/' || state.url === '/landing' || state.url === '/login') {
44
53
  this.router.navigate(['/home'], { queryParams: next.queryParams });
45
54
  return of(false);
46
55
  }
@@ -54,7 +63,6 @@ export class AuthGuard {
54
63
  return of(true);
55
64
  }
56
65
 
57
-
58
66
  // Then handle whether users have consented. If not, go to consent, otherwise skip past consent.
59
67
  if ((!dbUser.consented || dbUser.accessState === AccessState.CONSENT) && state.url !== '/consent') {
60
68
  this.router.navigate(['/consent'], { queryParams: next.queryParams });
@@ -2,7 +2,6 @@ import { Inject, Injectable, WritableSignal, inject, DestroyRef, computed } from
2
2
  import { toObservable } from '@angular/core/rxjs-interop';
3
3
  import { Subject, Observable, merge, forkJoin, of, from, pipe } from 'rxjs';
4
4
  import { startWith, pairwise, publishLast, publish, publishReplay, refCount, tap, pluck, mergeMap, filter, takeUntil, skipUntil, buffer, skip, switchMap, map, take } from 'rxjs/operators';
5
- import { patchState } from '@ngrx/signals';
6
5
  import { setEntities, setEntity, removeEntities, SelectEntityId } from '@ngrx/signals/entities';
7
6
  import { EntityLoadQuery, EntityStreamQuery, entityInQueryResults } from '../store/app.store';
8
7
  import { QueryParams, QueryOptions, AnyEntity } from '../store/app.model';
@@ -274,9 +273,11 @@ export class CachedListenersService {
274
273
  .map((dc) => dc.docData['__id']);
275
274
 
276
275
  // Patch all the changes to the store
277
- patchState(store, setEntities(entitiesToAdd, { selectId }));
278
- patchState(store, setEntities([...entitiesToModify, ...entitiesToModify2], { selectId }));
279
- patchState(store, removeEntities([...entitiesToRemove, ...entitiesToRemove2]));
276
+ store.handleStreamChanges(
277
+ entitiesToAdd,
278
+ [...entitiesToModify, ...entitiesToModify2],
279
+ [...entitiesToRemove, ...entitiesToRemove2],
280
+ );
280
281
  });
281
282
 
282
283
  return {
@@ -6,8 +6,7 @@ import { environment } from '../../../environments/environment';
6
6
  import { DocumentSnapshot, serverTimestamp, Timestamp, getDoc, getDocs, doc, setDoc, updateDoc, deleteDoc, docData, collection, collectionData, collectionChanges, query, where, orderBy, OrderByDirection, limit, startAt, startAfter, endAt, endBefore, DocumentChange, increment, AggregateQuerySnapshot, AggregateField, AggregateSpec, getAggregateFromServer, getCountFromServer } from '@angular/fire/firestore';
7
7
  import { AnyEntity, QueryParams, QueryOptions } from '../store/app.model';
8
8
  import { DatabaseService } from './database.service';
9
- import { SelectEntityId, setAllEntities } from '@ngrx/signals/entities';
10
- import { patchState } from '@ngrx/signals';
9
+ import { SelectEntityId } from '@ngrx/signals/entities';
11
10
  import { AuthMockDB } from '../store/auth/auth.mock';
12
11
 
13
12
  // Entity Model DB Data
@@ -35,8 +34,8 @@ export class FirebaseMockService implements DatabaseService {
35
34
  private injector: Injector,
36
35
  ) {
37
36
  // Init Entity Models
38
- patchState(this.DB['users'], setAllEntities(USER_DB, { selectId }));
39
- patchState(this.DB['userContexts'], setAllEntities(USERCONTEXT_DB, { selectId }));
37
+ this.DB['users'].init(USER_DB);
38
+ this.DB['userContexts'].init(USERCONTEXT_DB);
40
39
  }
41
40
 
42
41
  /** Creates a unique id */
@@ -1,7 +1,7 @@
1
1
  import { WritableSignal, inject } from '@angular/core';
2
2
  import { Timestamp, writeBatch } from '@angular/fire/firestore';
3
3
  import { patchState, signalStoreFeature, withMethods } from '@ngrx/signals';
4
- import { removeEntities, removeEntity, setEntities, setEntity, updateEntity, withEntities } from '@ngrx/signals/entities';
4
+ import { removeEntities, removeEntity, setEntities, setEntity, updateEntity, withEntities, setAllEntities } from '@ngrx/signals/entities';
5
5
  import { EntityChanges, EntityId, SelectEntityId } from '@ngrx/signals/entities/src/models';
6
6
  import { CachedListenersService } from '../firebase/cached-listeners.service';
7
7
  import { DATABASE_SERVICE, DatabaseService } from '../firebase/database.service';
@@ -58,6 +58,14 @@ export function withEntitiesAndSelectMethods<S extends AnyEntity>() {
58
58
  return signalStoreFeature(
59
59
  withEntities<S>(),
60
60
  withMethods((store) => ({
61
+ init(entities: S[]) {
62
+ patchState(store, setAllEntities<S>(entities, { selectId }));
63
+ },
64
+ handleStreamChanges(entitiesToAdd: S[], entitiesToModify: S[], entitiesToRemove: string[]) {
65
+ patchState(store, setEntities(entitiesToAdd, { selectId }));
66
+ patchState(store, setEntities(entitiesToModify, { selectId }));
67
+ patchState(store, removeEntities(entitiesToRemove));
68
+ },
61
69
  selectEntity(id: string): S {
62
70
  const result = store.entityMap()[id];
63
71
 
@@ -767,7 +775,7 @@ export function selectEntities<T>(entityMap: Record<string, T>, queryParams: Que
767
775
  return e[key] ? !val.some((v) => e[key].includes(v)) : true;
768
776
 
769
777
  case 'in':
770
- return !val.includes(e[key]);
778
+ return val.length > 0 && !val.includes(e[key]);
771
779
 
772
780
  case 'not-in':
773
781
  return val.includes(e[key]);
@@ -923,7 +931,9 @@ export async function processLoadQueries<T extends { __id: string }>(entities: T
923
931
 
924
932
  // Process queries concurrently using Promise.all
925
933
  await Promise.all(optimizedQueries.filter((q) => !!q).map(async (query) => {
926
- await query.store.load(query.queryParams, query.queryOptions, query.loadQueries);
934
+ if (!query.queryParams.some((param) => Array.isArray(param[2]) && param[2].length === 0 && param[1] === 'in')) {
935
+ await query.store.load(query.queryParams, query.queryOptions, query.loadQueries);
936
+ }
927
937
  }));
928
938
  }));
929
939
  }
@@ -23,5 +23,5 @@ export enum AccessState {
23
23
  CONSENT = '01 - consent', // on consent form
24
24
  SUBMIT_INTEREST = '02 - submit interest', // on basic interest form
25
25
  WAITING = '03 - waiting', // on waitlist for early access
26
- DONE = 'done', // finished with the entire flow
26
+ DONE = 'done', // finished with the access flow
27
27
  }
@@ -144,7 +144,7 @@ export class EarlyAccessComponent implements OnInit {
144
144
  mergeMap(async (user) => {
145
145
  const posNum = await this.userStore.count([
146
146
  ['joinedWaitlistAt', '<=', user.joinedWaitlistAt],
147
- ['accessState', '<', AccessState.DONE],
147
+ ['accessState', '==', AccessState.WAITING],
148
148
  ], {});
149
149
  return this.nth(posNum);
150
150
  }),
@@ -155,7 +155,7 @@ export class EarlyAccessComponent implements OnInit {
155
155
  filter((user: User) => !!user.joinedWaitlistAt),
156
156
  mergeMap(async (user) => {
157
157
  const total = await this.userStore.count([
158
- ['accessState', '<', AccessState.DONE],
158
+ ['accessState', '==', AccessState.WAITING],
159
159
  ], {});
160
160
  return `${total}`;
161
161
  }),
@@ -1,5 +1,5 @@
1
1
  <div class="navbar-container">
2
- <!--<img class="logo" src="assets/images/logo.svg">-->
2
+ <!--<img class="logo" src="images/logo.svg">-->
3
3
  @if (currentUser()) {
4
4
  <div class="user-setting-section">
5
5
  <img class="profile-pic" [src]= 'currentUser().photoURL' [matMenuTriggerFor]="menu" #menuTrigger/>
@@ -5,20 +5,20 @@
5
5
  box-shadow: -4px 3px 10px rgba(200, 224, 212, 0.25);
6
6
  display: flex;
7
7
  flex-direction: row;
8
- align-items: center; // Center items vertically
9
- padding: 8px 16px; // Add padding to the container
8
+ align-items: center;
9
+ padding: 8px 16px;
10
10
 
11
11
  .logo {
12
12
  width: 46px;
13
13
  height: 46px;
14
14
  cursor: pointer;
15
- margin-right: 16px; // Add margin between logo and user section
15
+ margin-right: 16px;
16
16
  }
17
17
 
18
18
  .user-setting-section {
19
- margin-left: auto; // Push to the right
19
+ margin-left: auto;
20
20
  display: flex;
21
- align-items: center; // Center items vertically
21
+ align-items: center;
22
22
  color: #2DBDB1;
23
23
  .profile-pic{
24
24
  height: 46px;
@@ -0,0 +1,31 @@
1
+ // Define the type of the environment variables.
2
+ declare interface Env {
3
+ readonly NODE_ENV: string;
4
+ NG_APP_FIREBASE_API_KEY: string;
5
+ NG_APP_FIREBASE_LOGS_API_KEY: string;
6
+ NG_APP_FIREBASE_DEV_API_KEY: string;
7
+ // Replace the following with your own environment variables.
8
+ // Example: NGX_VERSION: string;
9
+ // eslint-disable-next-line @typescript-eslint/no-explicit-any
10
+ [key: string]: any;
11
+ }
12
+
13
+ // Choose how to access the environment variables.
14
+ // Remove the unused options.
15
+
16
+ // 1. Use import.meta.env.YOUR_ENV_VAR in your code. (conventional)
17
+ declare interface ImportMeta {
18
+ readonly env: Env;
19
+ }
20
+
21
+ // 2. Use _NGX_ENV_.YOUR_ENV_VAR in your code. (customizable)
22
+ // You can modify the name of the variable in angular.json.
23
+ // ngxEnv: {
24
+ // define: '_NGX_ENV_',
25
+ // }
26
+ declare const _NGX_ENV_: Env;
27
+
28
+ // 3. Use process.env.YOUR_ENV_VAR in your code. (deprecated)
29
+ declare namespace NodeJS {
30
+ export interface ProcessEnv extends Env {}
31
+ }
@@ -1,9 +1,11 @@
1
1
  export const environment = {
2
2
  production: true,
3
3
  firebase: {
4
- // REPLACE WITH CONFIG
4
+ apiKey: import.meta.env.NG_APP_FIREBASE_API_KEY,
5
+ // REPLACE WITH REMAINING CONFIG
5
6
  },
6
7
  firebaseLogs: {
8
+ apiKey: import.meta.env.NG_APP_FIREBASE_LOGS_API_KEY,
7
9
  // REPLACE WITH CONFIG
8
10
  },
9
11
  };
@@ -4,8 +4,9 @@
4
4
 
5
5
  export const environment = {
6
6
  production: false,
7
- mockDB: true,
7
+ mockDB: false,
8
8
  firebase: {
9
+ apiKey: import.meta.env.NG_APP_FIREBASE_DEV_API_KEY,
9
10
  // REPLACE WITH CONFIG
10
11
  },
11
12
  };
@@ -1,14 +1,14 @@
1
1
  <!doctype html>
2
2
  <html lang="en">
3
3
  <head>
4
- <meta charset="utf-8">
4
+ <meta charset="utf-8" />
5
5
  <title><%= classify(project) %></title>
6
- <base href="/">
7
- <meta name="viewport" content="width=device-width, initial-scale=1">
8
- <link rel="icon" type="image/x-icon" href="favicon.ico">
9
- <link rel="preconnect" href="https://fonts.gstatic.com">
10
- <link href="https://fonts.googleapis.com/css2?family=Roboto:wght@300;400;500&display=swap" rel="stylesheet">
11
- <link href="https://fonts.googleapis.com/icon?family=Material+Icons" rel="stylesheet">
6
+ <base href="/" />
7
+ <meta name="viewport" content="width=device-width, initial-scale=1" />
8
+ <link rel="icon" type="image/x-icon" href="favicon.ico" />
9
+ <link rel="preconnect" href="https://fonts.gstatic.com" />
10
+ <link href="https://fonts.googleapis.com/css2?family=Roboto:wght@300;400;500&display=swap" rel="stylesheet" />
11
+ <link href="https://fonts.googleapis.com/icon?family=Material+Icons" rel="stylesheet" />
12
12
  </head>
13
13
  <body>
14
14
  <app-root></app-root>
@@ -0,0 +1,15 @@
1
+ /* To learn more about Typescript configuration file: https://www.typescriptlang.org/docs/handbook/tsconfig-json.html. */
2
+ /* To learn more about Angular compiler options: https://angular.dev/reference/configs/angular-compiler-options. */
3
+ {
4
+ "extends": "./tsconfig.json",
5
+ "compilerOptions": {
6
+ "outDir": "./out-tsc/app",
7
+ "types": ["node"]
8
+ },
9
+ "files": [
10
+ "src/main.ts"
11
+ ],
12
+ "include": [
13
+ "src/**/*.d.ts"
14
+ ]
15
+ }