ControlBird 0.1.49

v0.1.49
Platform

Features

  • schema: A new Schema Editor lets you define your own entity types. It shows every type as an inheritance tree with field counts, and you can create a type that inherits from one or more existing types, then edit its own fields - order, storage scope, default value - with the inherited fields listed alongside as read-only. Search keeps a match reachable by keeping its parents visible, so you can find a type without knowing where it sits.
  • schema: Removing a field now warns you what it actually does before you confirm, because the data in that field is removed from every existing instance.
  • schema: The types that ship with the platform are protected from changes that would alter their shape, and editing any type requires permission to do so.
  • services: A service that cannot start now reports why - it is waiting for its program, waiting for the content to arrive, or the program was rejected - and raises an alarm. Previously it appeared simply offline, which looks identical to a service that is stopped, restarting, or turned off, so a service that would never start on its own went unnoticed.

Bug Fixes

  • integrations: Integrations that deliver their own services install and run again. On 0.1.47 and 0.1.48 they could not, and the services they provide stayed stopped indefinitely with nothing reporting the cause. Upgrading from either release restores them.
  • restart: An entity created since the last checkpoint no longer comes back holding default values after a restart. It kept its identity but lost what had been written to it, and read back as a plausible wrong value rather than an error.
  • storage: A node now keeps all of its data under the directory it was started with. Depending on how it was launched, it could place part of its data elsewhere, so a backup or a copy of the data directory could capture only part of a node without saying so.
  • schema: Field definitions no longer require an explicit empty default for the kinds that have none, so authored schema documents are accepted as written instead of being rejected for a value there was no reason to state.