feat: update to bit v-9.11.0 #80 (#81)

Author: yasmoradi

.devcontainer/devcontainer.json

@@ -2,9 +2,9 @@
     "name": "Bit.TemplatePlayground",
     "image": "mcr.microsoft.com/dotnet/sdk:9.0",
     "hostRequirements": {
-        "cpus": 4
+        "cpus": 8
     },
-    "onCreateCommand": "dotnet workload install wasm-tools",
+    "onCreateCommand": "dotnet workload install wasm-tools && dotnet dev-certs https --trust",
     "waitFor": "onCreateCommand",
     "customizations": {
         "codespaces": {
@@ -14,23 +14,37 @@
         },
         "vscode": {
             "extensions": [
+                "GitHub.copilot",
                 "glenn2223.live-sass",
-                "kevin-chatham.aspnetcorerazor-html-css-class-completion",
+                "GitHub.copilot-chat",
+                "ms-dotnettools.csharp",
+                "ms-dotnettools.csdevkit",
+                "ms-azuretools.vscode-docker",
                 "DominicVonk.vscode-resx-editor",
-                "ms-dotnetools.csharp",
-                "ms-dotnettools.vscode-dotnet-runtime",
-                "ms-dotnettools.csdevkit"
+                "ms-vscode-remote.remote-containers",
+                "ms-dotnettools.blazorwasm-companion",
+                "ms-dotnettools.vscode-dotnet-runtime"
             ]
         }
     },
     "forwardPorts": [
-        4259,
+        2054,
+        2208,
+        2203,
+        4047,
         5000,
-        5215
+        5223
     ],
     "features": {
-        "ghcr.io/devcontainers/features/node": {},
-        "ghcr.io/devcontainers/features/python": {}
+        "ghcr.io/devcontainers/features/python": {},
+        "ghcr.io/devcontainers/features/powershell:1": {},
+        "ghcr.io/devcontainers/features/docker-in-docker:2": {},
+        "ghcr.io/devcontainers/features/node:1": { "version": "23" },
+        "ghcr.io/devcontainers/features/kubectl-helm-minikube:1": {
+            "version": "latest",
+            "helm": "latest",
+            "minikube": "latest"
+        }
     },
     "remoteEnv": {
         "ASPNETCORE_ENVIRONMENT": "Development"

.github/copilot-instructions.md

@@ -1,10 +1,11 @@
-# copilot-instructions.md
+# GitHub Copilot Instructions
+
+## Key Technologies
 
-### Technologies
 - **C# 13.0**
 - **ASP.NET Core 9.0**
 - **Blazor**: Component-based web UI framework
-- **.NET MAUI**: Cross-platform app development
+- **.NET MAUI Blazor Hybrid**: Cross-platform app development
 - **ASP.NET Core Identity**: Authentication and authorization
 - **Entity Framework Core**: Data access
 - **SignalR**: Real-time communication
@@ -15,7 +16,7 @@
 - **TypeScript**: Type-safe JavaScript development
 - **SCSS**: Advanced CSS preprocessing
 
-### Best Practices
+## Coding Conventions & Best Practices
 
 1.  **Follow the established project structure**: Adhere to the defined layout for consistency.
 2.  **Use Bit.BlazorUI Components**: Prioritize using components from the Bit.BlazorUI library over generic HTML to ensure UI consistency and leverage built-in features.
@@ -24,49 +25,26 @@
 5.  **Implement Structured Logging**: Use structured logging for clear, queryable application logs.
 6.  **Adhere to Security Best Practices**: Implement robust authentication and authorization patterns.
 7.  **Use Async Programming**: Employ `async/await` for I/O-bound operations to prevent blocking threads.
-8.  **Utilize Latest C# Features**: Write modern, concise, and efficient code by using the latest C# language features.
-9.  **Leverage Implicit Usings**: Take advantage of global using statements.
+8.   **Modern C#**: Write modern, concise, and efficient code by using the latest C# language features, including implicit usings and global using statements.
 10. **Respect .editorconfig**: Adhere to the `.editorconfig` file for consistent code style across all IDEs.
-12. **Prefer razor.cs code-behind files**: Use `.razor.cs` files for component logic instead of @code blocks in `.razor` files.
-13. **Prefer razor.scss files**: Use `.razor.scss` files for component styles instead of inline styles in `.razor` files.
-
-### Rules for Using DeepWiki
-
-The `deepwiki` MCP tool is essential for this project. Use it not only to answer questions but also to guide **code modifications**.
-For the topics below, you **MUST** consult `deepwiki` to find correct implementations and usage patterns before writing or changing any code.
+11. **Prefer razor.cs code-behind files**: Use `.razor.cs` files for component logic instead of @code blocks in `.razor` files.
+12. **Prefer razor.scss files**: Use `.razor.scss` files for component styles instead of inline styles in `.razor` files.
+13. **After applying changes, make sure project builds successfully**: Always verify that the project builds without errors after making changes.
 
-**RULE 1:** If a task (which includes answering a question or performing a code modification) involves the use of bit BlazorUI components (e.g., `BitButton`, `BitTooltip`, `BitTextField`), or refers to `bitplatform`, `bit Bswup`, `bit Butil`, `bit Besql`, or `bit Boilerplate`,
-you **MUST** use the `deepwiki` mcp tool to find the correct implementation and usage patterns before writing or changing any code.
+### Rules for Using MCP
 
-**RULE 1 Command:**
-`deepwiki fetch bitfoundation/bitplatform`
+**RULE 1:** If a task (question, code modification or review) involves the use of bit BlazorUI components (e.g., `BitButton`, `BitTooltip`, `BitTextField`),
+or refers to `bitplatform`, `bit Bswup`, `bit Butil`, `bit Besql`, or `bit Boilerplate`, or involves UI components without explicitly specifying their UI toolkit,
+you **MUST** use the deepwiki's `ask_question` mcp tool to find the correct implementation and usage patterns of `bitfoundation/bitplatform` deep wiki before writing or changing any code.
 
 **End of RULE 1**
 
-**RULE 2:** If a task (question or code modification) involves mappers, or refers to `mapperly`, `map`, `project`, or `patch`, you **MUST** use the `deepwiki` mcp tool to find the correct implementation before writing or changing any code.
-
-**RULE 2 Command:**
-`deepwiki fetch riok/mapperly`
+**RULE 2:** If a task (question, code modification, or review) involves Microsoft technologies such as C#, F#, ASP.NET Core, Microsoft.Extensions, NuGet, Entity Framework, Blazor or the `dotnet` runtime,
+you **MUST** use the `microsoft.docs.mcp` server to search Microsoft's latest official documentation for detailed and up-to-date information before responding to specific or narrowly defined questions.
 
 **End of RULE 2**
 
-**RULE 3:** If a task (question or code modification) involves .NET MAUI, or refers to `xaml`, `Android`, `iOS`, or `Windows`, you **MUST** use the `deepwiki` mcp tool to find the correct implementation before writing or changing any code.
-
 **RULE 3 Command:**
-`deepwiki fetch dotnet/maui`
-
-**End of RULE 3**
-
-**RULE 4:** If a task (question or code modification) involves Hangfire, or refers to `background job` or `recurring jobs`, you **MUST** use the `deepwiki` mcp tool to find the correct implementation before writing or changing any code.
-
-**RULE 4 Command:**
-`deepwiki fetch HangfireIO/Hangfire`
-
-**End of RULE 4**
-
-**RULE 5:** If a task (question or code modification) involves file storage, or refers to `fluent storage` or `S3`, you **MUST** use the `deepwiki` mcp tool to find the correct implementation before writing or changing any code.
-
-**RULE 5 Command:**
-`deepwiki fetch robinrodricks/FluentStorage`
+Use Playwright MCP tools like browser_navigate for URLs, browser_click for interactions, and browser_snapshot for page analysis.
 
-**End of RULE 5**
+**End of RULE 3**

.github/workflows/cd-production.yml

@@ -0,0 +1,14 @@
+name: Bit.TemplatePlayground Production CD
+
+on:
+  workflow_dispatch:
+  push:
+    branches: [ "main" ]
+
+jobs:
+  build_and_deploy_prod:
+    name: build and deploy to production
+    uses: ./.github/workflows/cd-template.yml
+    with:
+      ENV_NAME: Production
+    secrets: inherit