Service Stack - Translations: Difference between revisions
Jump to navigation
Jump to search
(Created page with "= Overview = Services that manage translations within the project. = Services = * Service - Translations * Service - Translations Graph = Deploy instructions = *...") |
No edit summary |
||
| Line 11: | Line 11: | ||
* [[Deploy service stack - Translations]] | * [[Deploy service stack - Translations]] | ||
= Complex Filter requests = | |||
<syntaxhighlight lang="JavaScript"> | |||
{ | |||
filterType: "XXX" // up to calling service | |||
type: "group", | |||
elements: | |||
[ | |||
{ | |||
type: "logical", | |||
logicalTag: "textTag_languageId_text", | |||
resultType: "mediaLinkProperty" | |||
textTag: "mediaLinkPropertyValue", | |||
languageId: "en", | |||
text: "Blue", | |||
subjectIdentifierPropertyName: "propertyId", | |||
caseSensitive: true | |||
}, | |||
] | |||
} | |||
</syntaxhighlight> | |||
- searches for specific and full text, optional case sensitive | |||
- finds an identifier property on the subjects node and stores in LogicalResults for the request | |||
- resultType must exist in request because want it to match filterType and Translation has no way of knowing filterType of request | |||
= Working documents = | = Working documents = | ||
[[:Category:Working_documents - Service Stack - Translations|Service Stack - Translations]] | [[:Category:Working_documents - Service Stack - Translations|Service Stack - Translations]] | ||
Revision as of 04:51, 4 September 2021
Overview
Services that manage translations within the project.
Services
Deploy instructions
Complex Filter requests
{
filterType: "XXX" // up to calling service
type: "group",
elements:
[
{
type: "logical",
logicalTag: "textTag_languageId_text",
resultType: "mediaLinkProperty"
textTag: "mediaLinkPropertyValue",
languageId: "en",
text: "Blue",
subjectIdentifierPropertyName: "propertyId",
caseSensitive: true
},
]
}
- searches for specific and full text, optional case sensitive - finds an identifier property on the subjects node and stores in LogicalResults for the request - resultType must exist in request because want it to match filterType and Translation has no way of knowing filterType of request