For my usecase, I have a large monolith with over 100 team members. The churn and merge conflicts are constant and painful.
The schema file is over 13k lines with over 600 tables. I’ve been playing with some monkey patching to generate ruby schema dumps into multiple files in a subdir, one table per file. It works, but I don’t look forward to future breaking changes. :) On Monday, October 14, 2019 at 11:04:44 AM UTC-7, Jake Moffatt wrote: > What kind of other changes have you needed? What features would you like an > API to provide? > > On Friday, October 11, 2019 at 5:33:00 AM UTC-7, ed wrote:I’d rather see a > public API that we could hook into safely. While the sorting sounds helpful, > I’ve needed other behavior changes in the ruby schema dumper too. > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-core+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-core/1a5a0c9d-180d-49f0-8056-41bb68c7449a%40googlegroups.com.
