Philip Theus (prev. Mueller)
Philip Theus (prev. Mueller)
OK, I'm thoroughly confused now. I couldn't reproduce the problem in that simple example today either. However, the problem still existed in my real world code. I started from the...
Oh yes, you're right - I completely missed the "subschemas don't forward annotations" part when I read through the discussion the first time. Thank you for the links. > The...
This seems like it is still a problem, @bastelfreak could you take a look?
Our problem would be solved by either restoring the way `record_errors` worked before, or adding an option that makes `validate` return the error objects, or by adding an option to...
The cleanest solution is to get the autoload paths from the app configuration... How are you handling autoload paths from engines?
yeah, I mean it's smart to do the guessing. For the active admin problem specifically, you could add a config option to exclude certain folders from the autoload paths? It'd...
> We could probably add an option to disable that behaviour? Doesn't it make sense to implicitly disable it when `autoload_roots` are explicitly supplied?
I don't have a `DATABASE_URL` env var on my application server, so I'd have to build it from the Rails configuration. I'll look into that. It would be nice for...
It seems that `asdf` should at least output some kind of error when there are staged changes in a plugin and you're running update
Note: I haven't been able to execute the tests locally; there doesn't seem to be documentation on how to do that. I assume I need to configure a database somehow?