Closed insidieux closed 3 years ago
Also see the related #189
Also see the related #189
Ok, i've watched issue and pull.
I have some questions:
MigrationSource
implementation, instead of changing behaviour of previous existed. Is it ok for you? Is there a reason why we need to break compatibility with older Go versions?
Is there a reason why we need to break compatibility with older Go versions?
No, there is no suitable reasons. I've just ask your opinion.
Would you prefer: to make me commits, comments to previous pull or send newest?
No, there is no suitable reasons. I've just ask your opinion.
Then let's not do that. We never break compatibility if we can avoid it.
Would you prefer: to make me commits, comments to previous pull or send newest?
Let's work together on the other PR.
Ok, thanks, now i'm closing this issue and provide some comments to related.
Is your feature request related to a problem? Please describe.
Since version 1.16 golang support native embedding with packages
embed
andio/fs
.Describe the solution you'd like
Update minimal golang required version to 1.16 and provide
MigrationSource
with supportembed.FS
. I'll provide pull request a little bit later.