v0.9.0

Generated Bonsai operators no longer include the device name in their label. A Parse or Format node shows only the selected register, such as DigitalInputs instead of Behavior.DigitalInputs, and the operator description includes the device instead.

A new documentation generator produces a reference page for each register, payload and mask of a device. Each page lists the names of the type and its members in both the C# and the Python interface, so one DocFX site can document both from the same device metadata.

Device metadata is now checked when it is loaded. Loading rejects metadata that the schema accepts but that would generate wrong code, for example a default value outside the declared range, a bit mask value that is not a single bit, or a mask type that does not exist.

What's Changed

• Unify payload naming across generators by @glopesdev in #153
• Standardize whitespace in firmware output by @glopesdev in #157
• Follow declared mask names in firmware output by @glopesdev in #158
• Support input pins with no trigger mode by @glopesdev in #160
• Emit mask defaults as member names by @glopesdev in #156
• Honor register defaults in Python payloads by @glopesdev in #161
• Emit register reference documentation by @glopesdev in #155
• Extract shared value metadata into a base class by @glopesdev in #162
• Validate default values when loading metadata by @glopesdev in #164
• Extend validation of device metadata on load by @glopesdev in #165
• Align value conversions between C# and Python by @glopesdev in #166
• Support masks up to 32 bits by @glopesdev in #167
• Align generated descriptions with device metadata by @glopesdev in #169
• Drop device prefix and revise descriptions by @glopesdev in #168
• Release the serial port when connection fails by @glopesdev in #170
• Wrap long fields in generated Python by @glopesdev in #171
• Document validation of device metadata on load by @glopesdev in #172

Full Changelog: v0.8.0...v0.9.0