mirror of
https://github.com/PepperDash/Essentials.git
synced 2026-02-12 11:15:08 +00:00
Updated Essentials Architecture (markdown)
@@ -83,7 +83,7 @@ At startup, the configuration file is read, and a ReadyEvent is fired. Upon bein
|
||||
|
||||
For example, a `DeviceConfig` object:
|
||||
|
||||
```
|
||||
```chasrp
|
||||
namespace PepperDash.Essentials.Core.Config
|
||||
{
|
||||
public class DeviceConfig
|
||||
@@ -123,7 +123,7 @@ This ordering ensures that all devices are at least present before building tie
|
||||
|
||||
In each device/room step, a device factory process is called. We call subsequent device factory methods in the various libraries that make up Essentials until one of them returns a functional device. This allows us to break up the factory process into individual libraries, and not have a huge master list of types and build procedures. Here's part of the code:
|
||||
|
||||
```
|
||||
```csharp
|
||||
// Try local factories first
|
||||
var newDev = DeviceFactory.GetDevice(devConf);
|
||||
|
||||
|
||||
Reference in New Issue
Block a user