Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding hint on migration name in CamelCase #943

Merged
merged 1 commit into from
Jan 21, 2017

Conversation

igorsantos07
Copy link
Contributor

@igorsantos07 igorsantos07 commented Aug 23, 2016

Nothing much to say besides I get annoyed as I never remember if the migrations should be snake_case as the file or CamelCase as the class. A tip about that on the help could be useful, instead of hitting the errorwall :)

@rquadling
Copy link
Collaborator

I wonder if snake_case and UpperCamelCase should both be accepted?

One thing I have locally is an amendment that allows me to apply a mask to the name. We enforce our devs to use DT_nnn_xxxx_xxxx_xxxx as the DTnnn number is our Jira task. That way, each migration is easily identifiable to a single task.

@robmorgan
Copy link
Member

@igorsantos07 thanks

@robmorgan robmorgan changed the base branch from 0.6.x-dev to master January 21, 2017 18:43
@robmorgan robmorgan merged commit f0a52eb into cakephp:master Jan 21, 2017
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.

3 participants