The generators currently fail in rails applications which are not using
activerecord, as the previous version relied on the table name
pluralization logic from that library. This changes to use the simpler
version which matches the way rails' default routes generator handles it.
The generators currently fail in rails applications which are not using activerecord, as the previous version relied on the table name pluralization logic from that library. This changes to use the simpler version which matches the way rails' default routes generator handles it.