Replace the buggy next_migration_number implementation with what ActiveR... #19
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
...ecord::Generators::Base already have.
The current implementation of next_migration_number generates VERSION numbers that are too long. This results in these migrations been run last every time even if other migrations are created after these. Resulting in issues like : #14
So just use what ActiveRecord::Generators::Base already have implemented.
https://github.com/rails/rails/blob/master/activerecord/lib/rails/generators/active_record.rb#L19