Colin Jones

@deluan Any interest in / openness to a PR that provides a workaround for using TypeScript? Pros: - Gets TypeScript migrations working. - Fairly uninvasive: adds a flag to each...

One additional caveat I just ran into that I wanted to call out: - `ctf-migrate bootstrap` writes `*.js` files which are easy enough to rename, but because it also stores...

@deluan Yep, absolutely, makes sense. It'll definitely be user-friendlier and seems like that approach could also allow migrations to be run in different languages (e.g. project started off in javascript...

:+1: I'm using this patch in my fork and left the existing arity in place for the jdbc consumer (trptcolin/blackwater@a069a534afe1ed9c70bfddcae1a03a2580af5cb7). I'm assuming there's some real solution for jdbc, but I...

Ah interesting, yeah this seems like a really useful feature - I'm surprised I haven't heard about it before! This one and the other issue you opened look like they...

Ah, yeah moved to `private`, OK. So maybe we can add a check for Rails version, and if it's 6+, change the `require_dependency` to `require`?

Ah, yeah I guess I was making an assumption there based on the "eliminates all known use cases for require_dependency, including STIs" language in [this Zeitwerk blog post](https://medium.com/@fxn/zeitwerk-a-new-code-loader-for-ruby-ae7895977e73) - but...

Yeah a whitelist of issues to skip would be my initial idea for a workaround here, and would help other use cases too (e.g. https://github.com/trptcolin/consistency_fail/issues/34)

Yep, totally, makes sense. I'm kind of wondering about similar use cases, but slightly different implementations too. When I've done this kind of thing in the past, I've used an...

I was thinking more like a config file passed to consistency_fail where you can say “ignore this association; I know about it already.” I’d rather not require users to decorate...