Codex ONLYOFFICE Flyway Migration for Document Metadata
Plan a sequential Flyway migration and keep the ONLYOFFICE integration starter's entity, mapper, repository and tests in sync.
中文Install in Codex
Open the ONLYOFFICE Integration Starter in Codex with existing migration versions, data classes and expected field behavior.
- Review `.agents/skills/onlyoffice-data-migrations/SKILL.md` and its requirements at the pinned GitHub commit.
- Create `.agents/skills/onlyoffice-data-migrations/` in your project and save the reviewed file as `.agents/skills/onlyoffice-data-migrations/SKILL.md`.
- Start Codex from that project's root, then type `$onlyoffice-data-migrations` and select the matching skill.
Example task
Map the changes for a proposed document metadata archive flag in this example.
{"latestMigration":10,"entity":"DocumentMetadataEntity","column":"archived","default":false}What to check
Propose `V11__add_archived_to_document_metadata.sql`, update the entity and mapping, and test the query result for default `archived=false`.
Original SKILL.md on GitHub · Updated
Frequently asked question
Which layer should own the new query condition?
Keep the condition in the service or repository. The repository owns persistence access.