At the time this migration is added to your project you haven't actually configured clearance yet. So it'd just spit out user anyway.

I had a version that defined the table as a single constant at the top of the file so at least you'd only have to change that In this version, the inlined `User` class set it's `table_name` attribute so it would be correct. Unfortunately, the generator itself assumes you're using `users` and thats how it determines which migration, if any, to copy/generate.

I can think of a few way to solve this (all of which I'd deem outside the purview of this PR):

1. Prompt the user for input when running the installer to ask what model they'd like to use.
2. Separate the install process out into generating the initializer in one step, asking them to configure that, and then generating migrations in another.

I'm not in love with any of these ideas, but I'd love to come up with something.