- Shipped
- August 14, 2026 at 8:06 PM UTC
- Author
- Kamo
- Commit
- c59b7ba
Whether a note is edited as rich text or plain text cannot be read back out of its content: a rich note nobody has formatted yet is byte-for-byte a plain one. Without a column the editor loses its toolbar every time the note is reopened. Defaulted TRUE, which is also what lets YugabyteDB add the column to a table that already has rows. TRUE specifically because every note written before the column existed was authored in the rich editor — it was the only editor there was — so backfilling to FALSE would show formatted notes as plain and offer to flatten them. @Order(0) for the usual reason: the moment shared-lib maps the column, every runner that loads a Note SELECTs it, so a late migration is never reached. Ships with the drift guard this package uses — it reflects the column name off the entity rather than restating it, and was checked by breaking the name and watching it fail. Applied against Yugabyte: column present as boolean default true, all existing rows backfilled to true, no NULLs.