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.
It is another api request for the extension. :)
Currently, we do autocomplete depend on the /api/v1/search/*. Each time users type in a character will invoke a search requests which brings in notable latency.
Since the number of our tags is less than 500 most of the time, it is ok to fetch all tags (< 10KB) into local memory one time and match them with users' inputs. In that situation, we don't need another http request until the user submit the link which will mitigate the latency during autocomplete.
Yes, we could fetch all tags by /api/v1/tags, however, we need to access the api recursively due to the pagination, which is not efficient.
Describe the solution you'd like
/api/v1/search/lists & /api/v1/search/tags might be able to accept a * to return all tags/links.
The text was updated successfully, but these errors were encountered:
Kovah
changed the title
[Feature Requeast] An Api that get all tags/links with least extra information
Add API query parameters to customize paginations
Jul 1, 2021
Linkace will accept a per_page query parameter which can be used to control how many items will be returned. Set it to 0 and all results will be returned. Any other number > 0 will limit the returned items to that amount.
Is your feature request related to a problem? Please describe.
It is another api request for the extension. :)
Currently, we do autocomplete depend on the
/api/v1/search/*
. Each time users type in a character will invoke a search requests which brings in notable latency.Since the number of our tags is less than 500 most of the time, it is ok to fetch all tags (< 10KB) into local memory one time and match them with users' inputs. In that situation, we don't need another http request until the user submit the link which will mitigate the latency during autocomplete.
Yes, we could fetch all tags by
/api/v1/tags
, however, we need to access the api recursively due to the pagination, which is not efficient.Describe the solution you'd like
/api/v1/search/lists
&/api/v1/search/tags
might be able to accept a*
to return all tags/links.The text was updated successfully, but these errors were encountered: