Skip to content

Conversation

@valentunn
Copy link
Contributor

  • Move active node tracking from prefs to db
  • Add default node change generic migration
  • Using migration above, change default nodes (remove web3, add Patract and onFinality)


@Database(
version = 18,
version = 20,
Copy link
Contributor

@FrogTravel FrogTravel May 13, 2021

Choose a reason for hiding this comment

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

Why we miss 19 version?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Because there are two migrations in PR - first one from 18 to 19, and second one from 19 to 20

}

@Suppress("ClassName")
class MoveActiveNodeTrackingToDb_18_19(private val migrator: PrefsToDbActiveNodeMigrator) : Migration(18, 19) {
Copy link
Contributor

Choose a reason for hiding this comment

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

And here we have migration from 18 to 19, but in another file we have version 20. Can you please help me with understanding why it is so? 🙃

Copy link
Contributor Author

Choose a reason for hiding this comment

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

In this PR i, in general, did two things:

  1. Move active node from prefs to DB
  2. Change default node set

I decided to do them in separate migration for readability and easier understanding of migrations. That's why there are 18 -> 19 and 19 -> 20 migrations

@valentunn valentunn merged commit aa1fd4e into develop May 14, 2021
@valentunn valentunn deleted the feature/change_nodes branch May 14, 2021 06:59
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.

3 participants