I got this strange behaviour when generating the migrations.

[laracasts]

I got this strange behaviour when generating the migrations.

[kadeprice]

That's how it was with the L4 Generator. I assume the script knows it's a new line because there is a space. You can't do it on the comma because then this wouldn't work
--schema="amount:double(15,2), customer_id:integer:index, customer_id:foreign:references('id'):on('customers'):onDelete('cascade')"

It would start a new line at (15,2). So the space is how it knows to start a new column.

Yeah - it's tough. I need some kind of split point for the regular expression. I've spent a lot of time trying to find a way to make this optional, but no dice.

The primary issue is that you can do:

--schema="username:string, age:integer"

If it were just this, then we could make the ,[space] optional. But the user can also pass arguments:

--schema="username:string, amount:decimal(1,2)

So, if somebody knows how to split that up into chunks, while allowing no spaces between each field:column, please do let me know. I haven't been able to figure out how.

The regex would need to give me, using the example above, an array with two items:

• username:string
• amount:decimal(1,2)

[BrandonSurowiec]

I did some searching and found how to separate using commas, as long as they weren't in parenthesis. Did some testing and this works for me:

$preg_split = preg_split('/,(?![^()]*+\\))/', $schema);
return array_map("trim", $preg_split);

I had to run trim on the array to get rid of the spaces that may appear in front when using commas and spaces.

[ I added a pull request: https://github.com//pull/9 ]

So this is fixed and merged now.

Thanks, all.