Assigning more fields to a grid stream down the road. What is the recommended approach and naming convention?

william - 2 months ago

@ryanthompson or someone.. Let’s say that i am in a project. Where is first built my grids using the gui. And know i wanna use migrations to assign fields to my grid stream…..

Im thinking i create an extension and use its migrations. Or should i rather use the database directory migrations for it?

What would you name such an extension? Would you let it stay in case you need to migrate more stuff? Or would you do this in your theme?

Trying to figure out a good strategy….For the sake of the discussion. Let’s say that i need to assign fields to a grid i am using on pages.

Answer

ryanthompson - 2 months ago

I always tend to put project specific seeds (content maybe) and migrations within the app directory. Here are some files that I recently used in a project the other day:

database/migrations/2017_09_26_162200_create_contact_variables.php
database/migrations/2017_09_26_163011_create_social_variables.php
database/migrations/2017_09_27_164452_create_download_variables.php
database/migrations/2017_09_28_170430_create_card_repeater.php
database/migrations/2017_09_29_202336_create_images_repeater.php

william - 2 months ago

ryanthompson [8:08 PM] : I tend to put project specific migrations right in the database/migrations directory. If an addon uses grid - then I would put them in that addon that uses it.

ryanthompson - 2 months ago

I always tend to put project specific seeds (content maybe) and migrations within the app directory. Here are some files that I recently used in a project the other day:

database/migrations/2017_09_26_162200_create_contact_variables.php
database/migrations/2017_09_26_163011_create_social_variables.php
database/migrations/2017_09_27_164452_create_download_variables.php
database/migrations/2017_09_28_170430_create_card_repeater.php
database/migrations/2017_09_29_202336_create_images_repeater.php