Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sort Migration Status #36

Merged
merged 2 commits into from
Jul 31, 2019
Merged

Sort Migration Status #36

merged 2 commits into from
Jul 31, 2019

Conversation

igbanam
Copy link

@igbanam igbanam commented Nov 13, 2018

When listing the migrations run with amber db status the list of
migrations needs to be ordered by the time this migrations were applied
so the developer can have a clearer, more defragmented idea of how the
schema of the application has changed over time.

To achieve this, this change

  • makes sure the list of migration is sorted by migrated_at before
    printing

Resolves #35

When listing the migrations run with `amber db status` the list of
migrations needs to be ordered by the time this migrations were applied
so the developer can have a clearer, more defragmented idea of how the
schema of the application has changed over time.

To achieve this, this change

* makes sure the list of migration is sorted by `migrated_at` before
printing

Resolves amberframework/migrate#35
@igbanam
Copy link
Author

igbanam commented Jan 24, 2019

This is awesome!

@faustinoaq
Copy link
Contributor

Hi @eliasjpr Are we sure this doesn't break Travis again? 😅

@igbanam
Copy link
Author

igbanam commented Jul 25, 2019

Is this still needed?

@eliasjpr eliasjpr merged commit 127307c into amberframework:master Jul 31, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Sort Migration Status
3 participants