Skip to content

docs(migrations): describe migration name generators - #197

Open
roxblnfk wants to merge 1 commit into
2.xfrom
docs/smg-15-name-generators
Open

roxblnfk wants to merge 1 commit into
2.xfrom
docs/smg-15-name-generators

Conversation

@roxblnfk

@roxblnfk roxblnfk commented Oct 5, 2026

Copy link
Copy Markdown
Member

🔍 What was changed

  • New «Migration Names» section: what NameBasedOnChangesGenerator (default) and ChangesCountNameGenerator produce, with real names from a run, how to switch to short names, and since which versions they exist.
  • The custom name generator example now implements the real generate(Atomizer $atomizer) signature and builds the name from the atomizer's tables.
  • The «Single File Strategy» example passes the required name generator to SingleFileStrategy.

Checklist

The section did not mention `ChangesCountNameGenerator`, which gives short names for migrations with many changes, and both examples failed: `SingleFileStrategy` was built without its required name generator, and the custom generator implemented `generate(array $changes)` instead of `generate(Atomizer $atomizer)`. Refs cycle/schema-migrations-generator#15.

Assisted-By: Claude Opus 5.5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant