added some docs

Author: sj-net

.prettierignore

@@ -8,4 +8,4 @@ assets/js/search-data.json
 assets/js/zzzz-search-data.json
 assets/js/just-the-docs.js
 *.md
-_includes/mermaid_config.js
+<!-- _includes/mermaid_config.js -->

_config.yml

@@ -87,10 +87,10 @@ search:
 enable_copy_code_button: true
 
 # By default, consuming the theme as a gem leaves mermaid disabled; it is opt-in
-mermaid:
+#mermaid:
   # Version of mermaid library
   # Pick an available version from https://cdn.jsdelivr.net/npm/mermaid/
-  version: "10.9.0"
+  #version: "10.9.0"
   # Put any additional configuration, such as setting the theme, in _includes/mermaid_config.js
   # See also docs/ui-components/code
   # To load mermaid from a local library, also use the `path` key to specify the location of the library; e.g.

_includes/head_custom.html

@@ -14,6 +14,10 @@
         position: absolute;
     }
 
+    pre.highlight {
+        padding-bottom: 12px !important;
+    }
+
     .highlight .p {
         color: #dee2f7 !important;
     }

docs/testing/moq.md

@@ -1,5 +1,5 @@
 ---
-title: MOQ
+title: MoQ
 parent: Testing
 layout: default
 published: true

quick.md gists.mdquick.md renamed to gists.md

@@ -14,6 +14,10 @@ permalink: /gists
     git cherry-pick <commit sha>
 ```
 
+``` powershell
+    git rebase origin/master
+```
+
 ### RoboCopy
 ---
 ```powershell

missing-things.md

@@ -0,0 +1,56 @@
+---
+layout: default
+title: Unofficial
+nav_order: 2
+description: "Things that are  not provided by default by the owner."
+permalink: /unofficial
+---
+
+# This page contains the concepts or code that most major libraries doesn't provide by default.
+
+
+## .NET 6+
+
+### Alias for DI.
+
+- .NET 6 doesn't have the proper alaising concept in the DI. So we can implement a Factory Pattern and solve this. 
+
+```csharp 
+
+public interface IDBContext 
+{
+    string Source {get;}
+
+    Database Database {get;}
+}
+
+
+public interface IDBContextFactory
+{
+    IDBContext GetDBContext(string source); // you can use a enum too here.
+}
+
+public class DBContextFactory : IDBContextFactory
+{
+    private readonly IEnumerable<IDBContext> _dbContexts;
+    public DBContextFactory(IEnumerable<IDBContext> dbContexts)
+    {
+        _dbContexts = dbContexts;
+    }
+
+    public IDBContext GetDBContext(string source)
+    {
+        return _dbContexts.Where(_=>_.Source == source).FirstOrDefault();
+    }
+}
+
+// registations in DI. 
+
+services.AddScoped<IDBContextFactory, DBContextFactory>();
+services.AddScoped<IDBContext, CartDBContext>(); // pass source as Cart and hard code that in the implementation
+services.AddScoped<IDBContext, OrderDBContext>();  // pass source as Order and hard code that in the implementation
+services.AddScoped<IDBContext, LogDBContext>();  // pass source as Log and hard code that in the implementation
+services.AddScoped<IDBContext, ProductsDBContext>();  // pass source as Products and hard code that in the implementation
+
+// You can use Enum as well and avoid strings. 
+```

my_best_practices.md

@@ -0,0 +1,42 @@
+---
+layout: default
+title: My Best Practices
+nav_order: 2
+description: "My Best Practices"
+permalink: /best-pactices
+---
+
+## MVC / Web API
+
+- If you have to read anything from HttpContext then always ensure you use an interface like below. This removes the burden of mocking HttpContext in unit tests. 
+
+```csharp 
+public interface ICustomHttpContextAccessor
+{
+    int GetProjectId();
+}
+
+public class CustomHttpContextAccessor
+{
+    public int GetProjectId()
+    {
+        // your logic to read the project id from route data or from query params or from claims etc. 
+    }
+}
+```
+
+In Unit Tests, you can easily mock `ICustomHttpContextAccessor`. .NET Core provides `IHttpContextAccessor`, but this provides the access to the HttpContext only. So it's good to have our own interface that can be common accross the project. You can inject the `IHttpContextAccessor` into `ICustomHttpContextAccessor`.
+
+## Design Patterns
+
+- Avoid using Service Locator Pattern as it causes lot of trouble when writing unit tests. 
+- It's totally OK to have more thna 5 parameters inside a constructor but when you pass `IServiceProvider` and resolve the required things inside constructor it's going to be painfull at some point in time. 
+
+## Database 
+- Check the cost of queries when working with stored procedures or views and optimize them before moving to production. 
+- Ensure proper indexes on table's with large data. Once I encountered a sitaution where fetching one record based on 4 conditions used to take 6 minutes. Once I created the index on the columns for all these 4 conditions it took less than 2 seconds. That's the beauty of indexes.
+
+## ORM (EF & EF Core)
+- Ensure to dispose the `DBContext` properly in Unit of Work. 
+- Always use Unit of Work pattern when you have to operate on multiple tables like a transaction. 
+- UoW must be scoped lifetime in DI and each instance must open it's own connection to the DB and close it in dispose.