You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[assembly:System.Diagnostics.CodeAnalysis.SuppressMessage("Style","CS8632:The annotation for nullable reference types should only be used in code within a nullable")]
Copy file name to clipboardexpand all lines: docs/mithril-shards/default-forge.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -17,4 +17,4 @@ After all shards are initialized, they are started by invoking their `StartAsync
17
17
18
18
From this moment, the forge is running.
19
19
20
-
When the application lifetime runs out (in the default scenario by pressing CTRL+C when running in console) `StopAsync` method is called and it calls `StopAsync` on all running shards allowing them to close properly.
20
+
When the application lifetime ends (in the default scenario by pressing CTRL+C when running in console) `StopAsync` method is called, which calls `StopAsync` on all running shards allowing them to close properly.
description: Mithril Shards implementation, Event Bus
4
+
5
+
---
6
+
7
+
--8<-- "refs.txt"
8
+
9
+
Event Bus is a simple implementation of the [publish/subscribe pattern](https://en.wikipedia.org/wiki/Publish%E2%80%93subscribe_pattern){:target="_blank"} which is a messaging pattern that allows two or more actors to publish messages and handle these messages without having a direct relationship between them.
10
+
11
+
Publishers don't know if the message they are publishing is handled and by whom, while subscribers do not know who was the publisher of a specific event: this means that components among Mithril Shards can be [loosely coupled](https://en.wikipedia.org/wiki/Loose_coupling){:target="_blank"}
Copy file name to clipboardexpand all lines: docs/mithril-shards/forge-builder.md
+1-2
Original file line number
Diff line number
Diff line change
@@ -7,12 +7,11 @@ description: Mithril Shards implementation, ForgeBuilder class
7
7
8
8
ForgeBuilder class represents the entry point of a Mithril Shards application, it allows to add a shard by calling the generic `AddShard` method, with different overloads that accept an optional strongly typed shard setting file with an optional setting file validator.
9
9
10
-
By using `ConfigureLogging` it's possible to configure logging, it's basically a wrapper on the inner hostbiulder ConfigureLogging method, you could use it to have a finer control over logging configuration and available providers, but the easier way to log is by using the available [SerilogShard] that uses Serilog to configure the logging and relies on a configurable setting file where you can specify which sink to use.
10
+
By using `ConfigureLogging` it's possible to configure logging, it's basically a wrapper on the inner [HostBuilder ConfigureLogging](https://docs.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.hosting.webhostbuilder.configurelogging?view=aspnetcore-1.1&viewFallbackFrom=aspnetcore-5.0){:target="_blank"} method, you could use it to have a finer control over logging configuration and available providers, but the easier way to log is by using the available [SerilogShard] that uses Serilog to configure the logging and relies on a configurable setting file where you can specify which sink to use.
11
11
You can find more details on its specific documentation page and an example of its usage in the [example project]
12
12
13
13
After declaring an instance we have to specify which implementation of Forge we want to use.
14
14
Actually the only available implementation is [DefaultForge] class.
0 commit comments