[advancedcontentfilter] Fix formatting in src/middlewares and doc/advancedcontentfilter

This commit is contained in:
Hypolite Petovan 2018-04-17 07:17:25 -04:00
parent b02724f867
commit acce253d8e
2 changed files with 14 additions and 19 deletions

View file

@ -45,14 +45,11 @@ A post will be collapsed if at least one rule matches, but all matching rule nam
- **booleans** - `true` and `false`.
- **null** - `null`.
A backslash (``\``) must be escaped by 4 backslashes (``\\\\``) in a string
and 8 backslashes (``\\\\\\\\``) in a regex::
A backslash (``\``) must be escaped by 4 backslashes (``\\\\``) in a string and 8 backslashes (``\\\\\\\\``) in a regex::
`"a\\\\b" matches "/^a\\\\\\\\b$/"`
Control characters (e.g. ``\n``) in expressions are replaced with
whitespace. To avoid this, escape the sequence with a single backslash
(e.g. ``\\n``).
Control characters (e.g. ``\n``) in expressions are replaced with whitespace. To avoid this, escape the sequence with a single backslash (e.g. ``\\n``).
### Supported Operators
@ -85,13 +82,11 @@ The component comes with a lot of operators:
* ``>=`` (greater than or equal to)
* ``matches`` (regex match)
To test if a string does *not* match a regex, use the logical ``not``
operator in combination with the ``matches`` operator:
To test if a string does *not* match a regex, use the logical ``not`` operator in combination with the ``matches`` operator:
'not ("foo" matches "/bar/")'
`not ("foo" matches "/bar/")`
You must use parenthesis because the unary operator ``not`` has precedence
over the binary operator ``matches``.
You must use parenthesis because the unary operator ``not`` has precedence over the binary operator ``matches``.
#### Logical Operators