-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Open
Labels
Good First IssueGood for learners that are new to TerasologyGood for learners that are new to TerasologySize: SSmall effort likely only affecting a single area and requiring little to no researchSmall effort likely only affecting a single area and requiring little to no researchType: RefactoringRequest for or implementation of pure and automatic refactorings, e.g. renaming, to improve clarityRequest for or implementation of pure and automatic refactorings, e.g. renaming, to improve clarity
Description
Motivation
Whitelist and blacklist are nowadays referred to using the more inclusive terms allowlist and denylist (or blocklist).
Due to the age and size of our codebase, in older parts of the code we still use the less inclusive terms, e.g. in (ServerConnectListManager.java)[https://github.com/MovingBlocks/Terasology/blob/develop/engine/src/main/java/org/terasology/engine/network/internal/ServerConnectListManager.java]
We want to demonstrate our openness and inclusiveness not only in how we treat people but also in our code, so this should be changed.
Proposal
Search our codebase for usages of "whitelist" and "blacklist" and refactor these usages to "allowlist" and "denylist".
Metadata
Metadata
Assignees
Labels
Good First IssueGood for learners that are new to TerasologyGood for learners that are new to TerasologySize: SSmall effort likely only affecting a single area and requiring little to no researchSmall effort likely only affecting a single area and requiring little to no researchType: RefactoringRequest for or implementation of pure and automatic refactorings, e.g. renaming, to improve clarityRequest for or implementation of pure and automatic refactorings, e.g. renaming, to improve clarity
Type
Projects
Status
No status
Status
No status