Copilot

> > > > > @copilot Did you see the images and the rest of the thread... there were interesting solutions there... > > ... I've implemented the multi-step migration...

> @copilot would that make sense that instead of doing something like the proposed solution: > > ```raku... Yes, both approaches make a lot of sense! Auto-generation from model differences...

> > @copilot would that make sense that instead of doing something like the proposed solution: > > > > ```raku... Both approaches make excellent sense! Auto-generation from model differences...

@copilot > @copilot > > > > > > @copilot would that make sense that instead of doing something like the proposed solution:... Implemented both the ClassHOW-based migration DSL and...

> @copilot the intention with ^migration is to be used by the migration code (probably the Cli code) to generate the SQL to be used on the populate part of...

> @copilot I was thinking... if the model versions are declared in different files (one file per version), I don't see a problem to use `:ver`. The different versions can...

> @copilot you do not need a `is ver`, the native `:ver` is enough, and if the files are located on a predictable place, you don't need registration. You're absolutely...

@shargon I've opened a new pull request, #1418, to work on those changes. Once the pull request is ready, I'll request review from you.

> @copilot I actually dont think we need the close button, these OS native notifications that Electron supports have an X as close button anyway. Otherwise looks good, go ahead...

> > > > > @copilot I actually dont think we need the close button, these OS native notifications that Electron supports have an X as close button anyway. Otherwise...