Summary
In T387331: Provide a mechanism for other extensions to modify protected variables access requirements, the associated mechanism was added. We should now customise the warning and errors messages in AbuseFilter to ensure that they make sense when a user lacks ability to see a specific set of protected variables
Background
- T387331 added the ability for other extensions to set additional restrictions for specific protected variables
- This was done so that CheckUser could define additional restrictions for user_unnamed_ip
- When implementing this feature, it was decided to split off customising the error messages into a new task to break down the work
Acceptance criteria
- When a user lacks access to a specific protected variable, the warning or error messages displayed indicate the specific variable and why this is the case