Rename wording to allowlist and blocklist
Background / User story
In continue to the discussion about wording in the products we will change our wording to allowlist and blocklist
What to change
- Design: N/A
- Research: N/A
- Spec: https://gitlab.com/eyeo/specs/spec/-/merge_requests/369
-
Legal: Please don't even ask
😇 - Development: We could run the changes against Manvel's (awesome) list here.
Hints for testers
- Besides of the changes in UI strings we have also renamed variables in codebase, so far no issue is noticed, but running generic tests(not only targeting UI) would be great, as we touched most of the codebase.
- Also we deprecated
whitelist
doclink in favor ofallowlist
, so would be great to ensure thatwhitelist
doclink is yet around for backwards compatibility and point to the same page asallowlist
doclink.
Hints for translators
Changed text of current strings:
devtools_header_state_allowlisted
firstRun_fair_description
options_allowlist_empty_1
options_allowlist_notification
problem_note
Changed description of current strings:
options_tab_allowlist
options_allowlist_description
options_allowlist_add
options_allowlist_placeholder_example
options_allowlist_empty_1
options_allowlist_empty_2
options_customize_showDevToolsPanel_tooltip
options_allowlist_notification
Integration notes
None.
Edited by Thomas Greiner