Skip to content

DEV: enhance tokenization docs with more references #1249

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Mar 4, 2025
Merged

DEV: enhance tokenization docs with more references #1249

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions content/develop/interact/search-and-query/advanced-concepts/escaping.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,6 +72,8 @@ changes that the tokenizer makes to the tags are:

This means that when you define a tag field, you don't need to escape any characters, except
in the unusual case where you want leading or trailing spaces to be part of the tag text.
However, you do need to escape certain characters in a *query* against a tag field. See
[Query syntax]({{< relref "/develop/interact/search-and-query/advanced-concepts/query_syntax#tag-filters" >}})
for more information about this.
However, you do need to escape certain characters in a *query* against a tag field. See the
[Query syntax]({{< relref "/develop/interact/search-and-query/advanced-concepts/query_syntax#tag-filters" >}}) and
[Exact match]({{< relref "/develop/interact/search-and-query/query/exact-match" >}}) pages for more information about escaping
and how to use [DIALECT 2]({{< relref "/develop/interact/search-and-query/advanced-concepts/dialects#dialect-2" >}}), which is required for
exact match queries involving tags.