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
This is a feature I personally want, which includes sorting the results by time uploaded.
What I have in mind is , not to populate superInput for this but instead have it near the bottom of the search as a floating menu, something like what unsplash has implemented. If it makes sense we could also move the search filters to the bottom menu to make proper use of the space.
The text was updated successfully, but these errors were encountered:
Till the above PR is merged and the api is exposed for the same, we'll have to use a post-search-filteration process of the default results.
This can be done in either of two ways :
Sort the UI results
Sort the API results
Sorting the API results would be more efficient and less complex.
On the UI side of things we can use a toggleSwitch to toggle sort. we can use the checked attribute of the element to sort within an if statement , inside searchLoader
we might also simulate few loadMore clicks to get more results and in turn more results that are newer, also making the time differences between search results more gradual.
This is a feature I personally want, which includes sorting the results by time uploaded.
What I have in mind is , not to populate superInput for this but instead have it near the bottom of the search as a floating menu, something like what unsplash has implemented. If it makes sense we could also move the search filters to the bottom menu to make proper use of the space.
The text was updated successfully, but these errors were encountered: