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

ExtensionPage: rename "Uninstall" to "Purge" #3123

Merged
merged 3 commits into from
Oct 26, 2021

Conversation

askvortsov1
Copy link
Sponsor Member

Fixes #2965

Changes proposed in this pull request:
Title says it all.

Reviewers should focus on:
Should we retain the translation key names? It's not completely breaking (things will still work), but lang packs will need to update their translations.

Screenshot

Necessity

  • Has the problem that is being solved here been clearly explained?
  • If applicable, have various options for solving this problem been considered?
  • For core PRs, does this need to be in core, or could it be in an extension?
  • Are we willing to maintain this for years / potentially forever?

Confirmed

  • Frontend changes: tested on a local Flarum installation.
  • Backend changes: tests are green (run composer test).
  • Core developer confirmed locally this works as intended.
  • Tests have been added, or are not appropriate here.

Comment on lines 158 to 160
'uninstall',
<Button icon="fas fa-trash-alt" className="Button Button--primary" onclick={uninstall.bind(this)}>
{app.translator.trans('core.admin.extension.uninstall_button')}
'purge',
<Button icon="fas fa-trash-alt" className="Button Button--primary" onclick={purge.bind(this)}>
{app.translator.trans('core.admin.extension.purge_button')}
Copy link
Member

Choose a reason for hiding this comment

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

I don't know of any extension that might be (if any) hooking into this, but we should probably avoid changing item list keys, as that'd be an easy breaking change.

Copy link
Sponsor Member Author

Choose a reason for hiding this comment

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

Any objections to keeping the old names now, and changing them with 2.0? Alternatively, we could add a deprecated dummy entry.

Copy link
Member

Choose a reason for hiding this comment

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

Any objections to keeping the old names now, and changing them with 2.0?

Sounds good to me

Alternatively, we could add a deprecated dummy entry.

That could work too, then we'd remove it in 2.0, I'm fine with either solutions

Copy link
Member

Choose a reason for hiding this comment

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

A dummy entry wouldn't make any difference, I don't believe. All our ItemList methods fail silently.

I think the bigger issue was that if someone was hiding this option for some reason, changing the key would make it re-appear. A dummy entry wouldn't change this behaviour.

Copy link
Sponsor Member Author

Choose a reason for hiding this comment

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

A dummy entry wouldn't make any difference, I don't believe. All our ItemList methods fail silently.

I think the bigger issue was that if someone was hiding this option for some reason, changing the key would make it re-appear. A dummy entry wouldn't change this behaviour.

Fair enough

@askvortsov1 askvortsov1 merged commit 2b0d556 into master Oct 26, 2021
@askvortsov1 askvortsov1 deleted the as/rename_uninstall_to_purge branch October 26, 2021 21:32
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.

Rename extension Uninstall button
3 participants