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

chore: Remove old dex migrations #625

Closed
wants to merge 1 commit into from

Conversation

jcompagni10
Copy link
Contributor

@jcompagni10 jcompagni10 commented Jul 11, 2024

Remove old dex migrations.

There are multiple incoming PRs (ie. #624) that conflict with these migrations. Since they are no longer necessary we can safely remove them.

Integration Test Run
https://github.com/neutron-org/neutron-tests/actions/runs/9897237914

pr0n00gler
pr0n00gler previously approved these changes Jul 15, 2024
@pr0n00gler pr0n00gler dismissed their stale review July 23, 2024 10:45

After a couple of considerations we think it's not safe to remove migrations from the module. Module is a separate entity and if i import it as a third-part developer i must get a guarantee that all changes made by developer in the code also reflected in the state by migrations. What do you think?

Copy link
Collaborator

@pr0n00gler pr0n00gler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After a couple of considerations we think it's not safe to remove migrations from the module. Module is a separate entity and if i import it as a third-part developer i must get a guarantee that all changes made by developer in the code also reflected in the state by migrations. What do you think?

@pr0n00gler pr0n00gler closed this Jul 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants