Updated ORM docs

Author: CharlieDigital

docs/.vitepress/config.mts

@@ -73,7 +73,7 @@ export default defineConfig({
               // { text: 'Records', link: '/pages/intermediate/records' },
               { text: 'Extension Methods', link: '/pages/intermediate/extension-methods' },
               { text: 'Iterators and Enumerables', link: '/pages/intermediate/iterators-enumerables' },
-              { text: 'Unit Testing', link: '/pages/intermediate/unit-testing' },
+              { text: '🚧 Unit Testing', link: '/pages/intermediate/unit-testing' },
               { text: 'Express vs Minimal API', link: '/pages/intermediate/express-vs-minimal-api' },
               { text: 'Nest.js vs Controller API', link: '/pages/intermediate/nest-vs-controller-api' },
               { text: 'Decorators vs Attributes', link: '/pages/intermediate/decorators-vs-attributes' },
@@ -88,9 +88,9 @@ export default defineConfig({
               { text: 'Generators and Yield', link: '/pages/advanced/generators-yield' },
               // { text: 'dynamic (ExpandoObject)', link: '/pages/advanced/dynamic' },
               { text: 'JSON Serialization', link: '/pages/advanced/json-serialization' },
-              { text: 'Reflection', link: '/pages/advanced/reflection' },
-              { text: 'Channels', link: '/pages/advanced/channels' },
-              { text: 'Source Generation (Roslyn)', link: '/pages/advanced/source-generation-roslyn' },
+              { text: '🚧 Reflection', link: '/pages/advanced/reflection' },
+              { text: '🚧 Channels', link: '/pages/advanced/channels' },
+              { text: '🚧 Source Generation (Roslyn)', link: '/pages/advanced/source-generation-roslyn' },
             ]
           },
           {
@@ -99,16 +99,16 @@ export default defineConfig({
             items: [
               { text: 'Switch Expression', link: '/pages/bonus/switch-expression' },
               { text: 'Partial Classes', link: '/pages/bonus/partial-classes' },
-              { text: 'Global Using', link: '/pages/bonus/global-usings' }
+              { text: '🚧 Global Using', link: '/pages/bonus/global-usings' }
             ]
           },
           {
             text: 'How Do I...',
             collapsed: true,
             items: [
-              { text: 'Set up Formatters?', link: '/pages/how-to/code-formatting' },
-              { text: 'Interface with the Backend?', link: '/pages/how-to/openapi-bindings' },
-              { text: 'Build for other Platforms?', link: '/pages/how-to/cross-platform-build' }
+              { text: '🚧 Set up Formatters?', link: '/pages/how-to/code-formatting' },
+              { text: '🚧 Interface with the Backend?', link: '/pages/how-to/openapi-bindings' },
+              { text: '🚧 Build for Other Platforms?', link: '/pages/how-to/cross-platform-build' }
             ]
           },
         ]

docs/pages/intermediate/databases-and-orms.md

@@ -240,7 +240,7 @@ model RaceResult {
   </template>
   <template #right>
 
-```csharp{3,4,11,17-20,25,31-35,42,45,46}
+```csharp{3,4,11,17-20,25,31-34,42,45,46}
 public class Database(DbConfig config) : DbContext {
   // 👇 These two define our schema
   public DbSet<Runner> Runners { get; set; } = null!;
@@ -777,7 +777,7 @@ export class AppController {
   </template>
   <template #right>
 
-```csharp{42,50,55-61}
+```csharp{42,50,55-60}
 // 📄 ResultsRepository.cs: Sample repository
 public class ResultsRepository(
   Database db // 👈 Injected via DI
@@ -836,8 +836,7 @@ public class AppController(
   public async Task<
     List<RunnerRaceResult>
   > GetTop10FinishesByRunner(string email) {
-    var results = await resultsRepository.Top10FinishesByRunner(email);
-    return [.. results];
+    return [.. await resultsRepository.Top10FinishesByRunner(email)];
   }
 }
 ```

docs/pages/intermediate/nest-vs-controller-api.md

@@ -2,7 +2,7 @@
 
 **Nest.js** builds on top of Express (or optionally Fastify) and introduces a **structured, modular architecture** with features like **decorator-based routing, dependency injection (DI), and controllers**, making it more comparable to **.NET Controller APIs** than plain Express.js. By enforcing a convention-driven approach similar to ASP.NET Core, Nest.js simplifies the development of scalable applications while integrating well with TypeScript’s strong typing. Its use of decorators for defining routes and DI for managing services closely resembles the approach used in .NET, making it feel more structured and maintainable than raw Express.
 
-However, **Nest.js does not match .NET in performance**. Since Nest.js runs on Node.js, it inherits the limitations of JavaScript’s single-threaded event loop, leading to potential bottlenecks in CPU-bound workloads. While Fastify can improve Nest’s performance over Express, it still cannot compete with **.NET’s high-performance Kestrel server**, which is optimized for multi-threading and asynchronous processing. That said, **Nest.js is more production-ready than Express**, as it includes built-in support for **authentication, validation, middleware, and structured DI**, reducing the need for third-party dependencies.
+Since Nest.js runs on Node.js, it inherits the limitations of JavaScript’s single-threaded event loop, leading to potential bottlenecks in CPU-bound workloads. While Fastify can improve Nest’s performance over Express, it still comes up short against **.NET’s high-performance Kestrel server**, which is optimized for multi-threading and asynchronous processing. That said, Nest.js is more production-ready than Express, as it includes built-in support for **authentication, validation, middleware, and structured DI**, reducing the need for third-party dependencies and more "batteries included".
 
 ::: tip If you're already using Nest.js
 If your team is already using Nest.js, chances are that there is a need for the more structured approach of Nest.js over Express.js.  In this case, you will find that .NET controller web APIs are conceptually similar, but probably overall easier to work with because of the type system (e.g. parameter type checking is automatic, OpenAPI schema bindings are "free")

docs/pages/intro-and-motivation.md

@@ -6,12 +6,16 @@ Over the years, .NET and C# have evolved heavily (as has Microsoft) and now ***"
 
 During that time, the language design of both C# and TypeScript (JavaScript as well) have *converged* more than other languages.  The two languages are now remarkably similar in their core syntax such that developers that know one can typically pick up the other fairly easily.
 
-This guide aims to provide a walkthrough of just how similar these two languages are, but also highlight where C# and .NET can solve some of the pain points that many teams using TypeScript *on the backend* will no doubt encounter.
+This guide aims to provide a walkthrough of just how similar these two languages are and in fact can be used bi-directionally. In many cases, it will highlight where C# and .NET can solve some of the pain points that many teams using TypeScript *on the backend* will no doubt encounter.
 
 ::: tip Don't forget to check the repo!
 Many of the code examples in this guide are actually in [the GitHub repo](https://github.com/CharlieDigital/typescript-is-like-csharp).  Be sure to check it out so you can see the full examples and play around with the code yourself.
 :::
 
+::: info
+This guide was inspired by the [Kotlin is Like C#](https://ttu.github.io/kotlin-is-like-csharp/) guide I came across while learning Kotlin.
+:::
+
 ## Are They *Really* Similar?
 
 Before you ready your pitchforks, check out some of the similarities between TypeScript and C#:

src/csharp/ef-api/Controllers/AppController.cs

@@ -14,8 +14,7 @@ ResultsRepository resultsRepository
 
   [HttpGet("/top10/{email}")]
   public async Task<List<RunnerRaceResult>> GetTop10FinishesByRunner(string email) {
-    var results = await resultsRepository.Top10FinishesByRunner(email);
-    return [.. results];
+    return [.. await resultsRepository.Top10FinishesByRunner(email)];
   }
 
   [HttpGet("/results/{email}")]