Snake-cased

The model name may be given in camel-cased or snake-cased format, and options can be provided if you want to automatically populate the resulting migration with column information.

This list is stored as a Hash, where each key is a “snake-cased” representation of the class name and each value is a Class object representing the class itself.

It’s idiomatic to use lowercased, snake-cased field names.

The argument of the command should be a snake-cased description of what the migration will do: $ php artisan make:migration create_listings_table

awrence converts snake-cased Hash keys to camel case, which you can then convert to camel-cased JSON.

This is because, as discussed in Appendix B, the dummy app mounts the engine under test at its snake-cased name by default, which is app_component in our case.

For starters, the names are all camel cased rather than snake cased, and you can also pass in a parameter that specifies the amount of items in the ItemStack to be returned.

By convention, class names are capitalized (Animal), variable names are lower-cased (fido), and function names are “snake-cased” (compute_square_root()).

Each field definition includes a type, a snake-cased name, and a field number unique to the message.