Skip to content

Commit b6ececd

Browse files
committedMar 10, 2025··
Update links
1 parent 4f48427 commit b6ececd

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed
 

‎README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ Part of the curated [**FullStacksDev Angular and Firebase tech stack**](https://
44

55
This is a fairly simple **Logbook app** — to keep a single time-ordered log of text entries — focused on showcasing and learning the tech stack, built from the [base template](https://github.com/FullStacksDev/angular-and-firebase-template).
66

7-
You can read more about the [purpose and specs of the example apps](TODO) on our website.
7+
You can read more about the [purpose and specs of the example apps](https://fullstacks.dev/the-simple-example-apps) on our website.
88

99
## Running the app locally
1010

‎docs/3.data-model-and-access.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@
66

77
The backbone of most apps is the data model, and how it's accessed and updated.
88

9-
Revisiting the [spec of the simple example app](TODO) we see that only one logbook is required per logged-in user, and a logbook consists of a flat list of time-ordered _entries_. This is a fairly simple and common data model for many apps and can be modeled as a single "table" (or "collection", in Firestore) of data items differentiated per user.
9+
Revisiting the [specs of the simple example app](https://fullstacks.dev/the-simple-example-apps#app-specs) we see that only one logbook is required per logged-in user, and a logbook consists of a flat list of time-ordered _entries_. This is a fairly simple and common data model for many apps and can be modeled as a single "table" (or "collection", in Firestore) of data items differentiated per user.
1010

1111
This list of entries is stored in Firestore in a single collection called `entries`. Each entry is associated with a user via a `userId` field, which matches their Firebase Auth user ID. We then use security rules to control access — i.e. to ensure that a user can only retrieve and modify their own entries. We access all data from the frontend (so no server-side access in this case), using the Firebase JavaScript SDK, where we convert data from Firestore into strongly typed objects using TypeScript, within an Angular service that wraps all access to Firestore.
1212

0 commit comments

Comments
 (0)
Please sign in to comment.