Sammy Smallman

fix: Incorrect key/values within set_request

1

Closes #21 Signed-off-by: Sam Smallman

Set request contains "units" and "prefixPower". It shouldn't

Uniqueness

14

Schemas at the moment are inferred to be the same/valid for all devices by the absence of a `device_model_id`, `software_version_id` and `root` boolean value. If that is the case, these...

Manufacturer specific E1.20 schemas

2

There is a plausible scenario where a manufacturer may want to write a manufacturer specific version of an E1.20 parameter, for example: ``` { "scope": { "esta_manufacturer_id": 12345, "device_model_id": 1337,...

Referencing #14 I'm pulling out the "Informs/Informed By" extension into its own issue for discussion. There are currently two areas i can think of where it is useful to know...

Referencing #14 and @peternewman comment I'm pulling out the general concept of extensions, allowing a schema to contain meta data alongside a parameters data definition. A few topics up for...

Provide Context

1

Schemas currently provide a good definition of the payload to and from a responder but little context about a parameter. In their current state a controller can only assume certain...

Adding support for Swift Package Manager

2

Is there any chance we could pull the frameworks via SPM?

Provide consistent field names across parameters

2

Closes #23 Signed-off-by: Sam Smallman

Consistent Field Names

2

Fields duplicated across parameters should use the same "name" value. For example DEVICE_INFO contains the personality index and dmx start address, but uses different names for those fields rather than...