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

Rename "Rocket Chat Admin" role to "Keybase Admin" #4232

Merged
merged 1 commit into from
May 5, 2020

Conversation

cbeams
Copy link
Contributor

@cbeams cbeams commented May 4, 2020

Per bisq-network/roles#79 (comment)

Note that the ROCKET_CHAT_ADMIN enum label has not been renamed for
the backward compatibility reasons discussed in BondedRoleType Javadoc.

See also bisq-network/roles#60.

Per bisq-network/roles#79 (comment)

Note that the ROCKET_CHAT_ADMIN enum label has not been renamed for
the backward compatibility reasons discussed in BondedRoleType Javadoc.

See also bisq-network/roles#60.
@cbeams cbeams self-assigned this May 4, 2020
Copy link
Member

@sqrrm sqrrm left a comment

Choose a reason for hiding this comment

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

utACK

There is no need to change all the displayStrings language files, just changing the main one is enough.

@sqrrm
Copy link
Member

sqrrm commented May 5, 2020

I think renaming the enum shouldn't be a problem either.

@ManfredKarrer this touch DAO code, just a comment, but still.

Copy link
Contributor

@ManfredKarrer ManfredKarrer left a comment

Choose a reason for hiding this comment

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

utACK

@ManfredKarrer
Copy link
Contributor

I think renaming the enum shouldn't be a problem either.

I assume as well, but not sure if testing effort is worth it.

@sqrrm sqrrm merged commit f720764 into bisq-network:master May 5, 2020
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