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
Is your feature request related to a problem? Please describe.
Implementing unified search on clients as it is now requires parsing the { "entries": [ { "resourceUrl": ... to get the relevant data. This is a very unclean solution.
Describe the solution you'd like
As was mentioned in 2nd the linked issue, the files provider uses the attributes key to provide additional metadata. A similar approach could be used here, where roomToken would be the most important, but other info could be useful as well.
Example: > http://localhost/ocs/v2.php/search/providers/talk-message/search?format=json&term=test
Is your feature request related to a problem? Please describe.
Implementing unified search on clients as it is now requires parsing the
{ "entries": [ { "resourceUrl": ...
to get the relevant data. This is a very unclean solution.Describe the solution you'd like
As was mentioned in 2nd the linked issue, the files provider uses the
attributes
key to provide additional metadata. A similar approach could be used here, whereroomToken
would be the most important, but other info could be useful as well.Example:
> http://localhost/ocs/v2.php/search/providers/talk-message/search?format=json&term=test
Describe alternatives you've considered
As said, the only other solution I see is parsing the url manually.
Additional context
The text was updated successfully, but these errors were encountered: