fix: expressions in concordance search glossaries (crowdin#399)

Co-authored-by: Nazar Lysyi <[email protected]>
turkdevops · Jul 3, 2024 · 60758d2 · 60758d2
1 parent fe13092
commit 60758d2
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 3 deletions.
diff --git a/src/glossaries/index.ts b/src/glossaries/index.ts
@@ -440,7 +440,11 @@ export namespace GlossariesModel {
     export interface ConcordanceSearchRequest extends PaginationOptions {
         sourceLanguageId: string;
         targetLanguageId: string;
-        expression: string;
+        expressions: string[];
+        /**
+         * @deprecated
+         */
+        expression?: string;
     }
 
     export interface ConcordanceSearchResponse {

diff --git a/tests/glossaries/api.test.ts b/tests/glossaries/api.test.ts
@@ -312,7 +312,7 @@ describe('Glossaries API', () => {
                 {
                     sourceLanguageId: termLanguageId,
                     targetLanguageId: termLanguageId,
-                    expression: 'Welcome!',
+                    expressions: ['Welcome!'],
                 },
                 {
                     reqheaders: {
@@ -482,7 +482,7 @@ describe('Glossaries API', () => {
         const res = await api.concordanceSearch(projectId, {
             sourceLanguageId: termLanguageId,
             targetLanguageId: termLanguageId,
-            expression: 'Welcome!',
+            expressions: ['Welcome!'],
         });
         expect(res.data.length).toBe(1);
         expect(res.data[0].data.glossary.id).toBe(glossaryId);