Brendon Muir

Closing due to inactivity.

No further feedback, so closing this issue.

Since there was no further communication I'll close the issue.

Open to fixing this if it's still an issue. Let me know and I'll reopen.

Hi @vanboom, it's intended to be annoying. It's not supported and can cause subtle problems so I think it's best that it fatally fails. I'd assume you'd only find yourself...

Ah I see, yes that would be annoying. Is there a way to prevent a raise in migrations and only have it happen on normal app server boot, perhaps even...

Another idea is to allow the error raise to be silenced by an initialiser?

Thanks @vanboom. I'd only be ok with that solution if it didn't adversely affect the majority of people using the gem. If there's a way to cache the check when...

Closing this for now. See my comment in the PR.

Closing due to inactivity. This is still one of the downsides of the gem. Happy to look at a fresh PR that addresses this.