Column not created in migration for _ids variant of super_select fields

[jagthedrummer]

I did this:

rails g super_scaffold Category Team name:text_field related_team_ids:super_select{class_name=Team}

And the migration didn't include a column for related_team_ids.

But if I do the singular version like this:

rails g super_scaffold Category Team name:text_field related_team_id:super_select{class_name=Team}

then a column is created for related_team_id.

[jagthedrummer]

After looking at this I think that it's user error. I probably should have generated a join model first. That bit of the documentation could probably stand to be clearer. I had originally thought that I'd get an array column that would hold a collection of Team ids. (Which might be a nice thing to be able to do somehow. Similar to how we store role_ids on the Membership model.)

[jagthedrummer]

Seems like in this case we should warn the user that the use of _ids in the field name would seem to imply that they need a join model but that we can't find one. And we could recommend using {vanilla} like we do for singular _id columns.

https://github.com/bullet-train-co/bullet_train-core/blob/9b7f280d3a981b11f8f925e946ebff4c1d029436/bullet_train-super_scaffolding/lib/scaffolding/script.rb#L142-L183