ADD RxDB Case Study #1385
ADD RxDB Case Study #1385
Conversation
built with Refined Cloudflare Pages Action⚡ Cloudflare Pages Deployment
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1385 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 10 10
Lines 373 387 +14
Branches 94 103 +9
=========================================
+ Hits 373 387 +14 ☔ View full report in Codecov by Sentry. |
|
Thanks a lot @pubkey ! @json-schema-org/tsc I did an initial review and I would love yours too 🙏🏻 |
pages/blog/posts/rxdb-case-study.md
Outdated
|
|
||
| To improve developer experience, RxDB offers a [built-in way](https://rxdb.info/tutorials/typescript.html) to infer the document's TypeScript type from the schema during runtime. This is helpful because you get immediate feedback in your IDE: As soon as you update the schema, TypeScript picks up the changes. You'll see type errors in your code if you attempt to use fields that are no longer valid or if you forget to include newly required fields. | ||
|
|
||
| Below is an example on how to interfere the TypeScript type of a document from its JSON-schema: |
There was a problem hiding this comment.
"interfere" here is presumably supposed to be "infer"?
pages/blog/posts/rxdb-case-study.md
Outdated
| }, | ||
| /* ...other fields... */ | ||
| }, | ||
| required: ['firstName', 'lastName', 'passportId'], |
There was a problem hiding this comment.
It's completely irrelevant to the article but a pet peeve in database structures is having first and last name fields (rather than just a "name") field (c.f. https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/)
|
Thank you @Julian |
What kind of change does this PR introduce?
Adds the RxDB Case Study to the Blog.
Issue Number:
Related: pubkey/rxdb#6787
Screenshots/videos:
If relevant, did you update the documentation?
http://localhost:3001/blog/posts/rxdb-case-study
Summary
Does this PR introduce a breaking change?
No