Problem
If an app already has a devices table, there's no straightforward way to point the gem at it. The current workaround is subclassing ActionPushNative::Device, setting self.table_name, and/or overriding self.base_class to avoid Rails treating it as STI.
Proposed solution
Allow the table name to be configured via the install generator or an initializer. Something like config.table_name = "devices" would cover it. happy to submit a PR if this makes sense.
Problem
If an app already has a devices table, there's no straightforward way to point the gem at it. The current workaround is subclassing ActionPushNative::Device, setting self.table_name, and/or overriding self.base_class to avoid Rails treating it as STI.
Proposed solution
Allow the table name to be configured via the install generator or an initializer. Something like config.table_name = "devices" would cover it. happy to submit a PR if this makes sense.