Understanding the search syntax
When searching Lingohub, you can construct queries that match specific numbers and words. Some keys are available just inside the Editor search panel, but if you need to specify the search more, find the additional syntax below.
Negating the search
Most of the search syntax supports the prefix not: E.g., navigation not:in:key searches for all segments that don't have a key containing the text navigation.
Query for values greater or less than another value
You can use >, >=, <, and <= to search for values that are greater than, greater than or equal to, less than, and less than or equal to another value. You can also use range queries to search for values that are greater than or equal to, or less than or equal to, another value.
These modifiers are possible in in:id and createdAt
Query for values between a range
You can use the range syntax n..n to search for values within a range, where the first number n is the lowest and the second is the highest.
Query for dates
You can search for dates that are earlier or later than another date, or that fall within a range of dates, by using >, >=, <, <=, and range queries. Date formatting must follow the ISO8601 standard YYYY-MM-DD (year-month-day).
Use quotation marks for queries with whitespace
If your search query contains whitespace, you must surround it with quotation marks. For example:
cats NOT "hello world" matches repositories with the word "cats" but not the words "hello world."
build label: "bug fix" matches issues with the word "build" that has the label "bug fix."
Some non-alphanumeric symbols, such as spaces, are dropped from code search queries within quotation marks so that results can be unexpected.
Search by the key, description, or content
Qualifier | Example |
in:key navigation | matches segments that have "navigation" in the key |
Negating the search in:key
Qualifier | Example |
not:in:key navigation | matches segments that do not have "navigation" in key |
Qualifier | Example |
in:description test | matches segments that have "test" in description |
Negating the search in:description
Qualifier | Example |
not:in:description test | matches segments that do not have "test" in description |
Qualifier | Example |
in:text:Lingohub | matches segments that have "Lingohub" in text |
Note:
This modifier should occur only once. Only the first one will be used if it is added multiple times in the text. Further, the free search text will be taken from the whole query, e.g., this will be searched in:key but also this text.
Search by id
Qualifier | Example |
in:id:1 | in:id: matches segments having the id 1 |
It is possible to use closed ranges like in:id:1..5 and less/greater like in:id:>=5
Search in projects and branches
Qualifier | Example |
in:project:Rails/main | matches text segment which are in the project Rails and the main branch. |
It is possible to search in multiple projects like in:project:Rails,Angular or in just the branch in:project:/main
Search by status
Possible values: not_translated, prefilled, draft, translated, approved
Qualifier | Example |
is:status:draft | matches text segment which are in the draft status. |
Search by deleted and translatable
Qualifier | Example |
is:translatable | matches segments which are translatable. |
is:deleted | matches segments which are deleted. |
Search by created at and updated at
Qualifier | Example |
created:>2020-11-15 | matches segments that were created after November 15, 2020. |
updated:>=2020-11-15 | matches segments that were updated after November 15, 2020. |
Search by label
Qualifier | Example |
label:blue | matches segments which have the label blue attached. |
Qualifier “and” allow to concatenate multiple values and extend the search syntax.
Qualifier | Example |
in:id:2..5(and)in:text:user | matches segments that have Id between 2 and 5, and contain the word “user.” |
Congratulations! You have finished the article about search syntax. We hope that it helped you find answers to all your questions. Otherwise, contact our support, and we will gladly help!