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

Fix wording for globs in policy lists #1165

Merged
merged 2 commits into from Jul 11, 2022
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
@@ -0,0 +1 @@
Clarify that policy rule globs work like ACL globs. Contributed by Nico.
2 changes: 1 addition & 1 deletion content/client-server-api/modules/moderation_policies.md
Expand Up @@ -91,7 +91,7 @@ included in the ban list.
#### Events

The `entity` described by the state events can contain `*` and `?` to
match zero or more and one or more characters respectively. Note that
match zero or more characters and exactly one character respectively. Note that
rules against rooms can describe a room ID or room alias - the
subscriber is responsible for resolving the alias to a room ID if
desired.
Expand Down
2 changes: 1 addition & 1 deletion data/event-schemas/moderation_policy_rule.yaml
Expand Up @@ -15,7 +15,7 @@ properties:
entity:
description: |-
The entity affected by this rule. Glob characters `*` and `?` can be used
to match zero or more and one or more characters respectively.
to match zero or more characters or exactly one character respectively.
type: string
recommendation:
description: The suggested action to take. Currently only `m.ban` is specified.
Expand Down