Add morphs helper to blueprint

[girardinsamuel]

Added morphs to ease polymorphism relationships creation.
Still following Like,Article,Comment example we can now do:

# likes migration
table.morphs("record")

• I did not setup an index automatically (between record_type and record_id) as done in Orator, should we do that ?
• I just created a test for proof, but what's the policy for testing "blueprints columns", they seems not tests except few, should I remove the test ? And should we do it for each connection ?

[girardinsamuel]

@josephmancuso ready for review with some questions

[josephmancuso]

Looks great.

[josephmancuso]

hmm. What about in the case someone does:

table.morphs('record').nullable()

? We might have to add self._last_column as a list or tuple and then nullable will act on all the elements in the list? Same actually goes for table.timestamps() too

[girardinsamuel]

I did not thought about that, I'll look into it

[girardinsamuel]

@josephmancuso and what about this part :

I did not setup an index automatically (between record_type and record_id) as done in Orator, should we do that ?

[josephmancuso]

I did not setup an index automatically (between record_type and record_id) as done in Orator, should we do that ?

I don't see why not. Maybe have that as a parameter. morphs(indexes=True). have it default to true

[girardinsamuel]

@josephmancuso Here I deal with multiple columns locally in nullable() method but we could also have done it globally in the Blueprint class by always using self._last_column as a list.
Don't know what's best