You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello!
Are there plans to add a more flexible API for glossaries?
I'm interested in the case of integration with systems that have no database storage and need to be filtered by user_id.
That means when creating a glossary, i can specify an optional parameter and use it later in request to get all glossaries by a specific param. /v2/glossaries/{param_id}
Because now it could be done only by glossary ID (which changes every time the glossary is changed)
At the moment, without using system internal DB, I see an only option to specify a name like user_1-glossary_name in order to determine the ownership of glossaries within the system.
However, even after receiving them through get_all_glossaries, I will have to do internal complex filtering by parsing the name param.
Thank you!
The text was updated successfully, but these errors were encountered:
Hello!
Are there plans to add a more flexible API for glossaries?
I'm interested in the case of integration with systems that have no database storage and need to be filtered by user_id.
That means when creating a glossary, i can specify an optional parameter and use it later in request to get all glossaries by a specific param.
/v2/glossaries/{param_id}
Because now it could be done only by glossary ID (which changes every time the glossary is changed)
At the moment, without using system internal DB, I see an only option to specify a name like user_1-glossary_name in order to determine the ownership of glossaries within the system.
However, even after receiving them through get_all_glossaries, I will have to do internal complex filtering by parsing the name param.
Thank you!
The text was updated successfully, but these errors were encountered: