Using bindata is not ideal at all, but it's the only thing supported by golang-migrate/migrate.
I left maxVersion as a constant, I don't think it's worth to handle it properly for now. If we add a new migration there is no risk to forget to update it, because sync will complain about it.
Fix #18.
Using bindata is not ideal at all, but it's the only thing supported by
golang-migrate/migrate.I left
maxVersionas a constant, I don't think it's worth to handle it properly for now. If we add a new migration there is no risk to forget to update it, becausesyncwill complain about it.