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
Describe the bug
it seems that pagination is not taking into account for the OMDB API. Example, when you search on "Seven", you only get a few results in the api but if you add the pagination, you get the next results.
Example: https://www.omdbapi.com/?s=Seven&apikey=[your_Api_Key]&page=4
To Reproduce
Search for Seven: you will only see a few results
Go on the url with your API Key and add &page=2 ... you will see the other results (for sure, depending on the search, there might be a lot of pages).
Expected behavior
Either a scroll or a pagination could be helpful because right now, some movies are missing.
Screenshots
Occurs on
Tested on Windows. No idea for the others but I guess the behaviour is the same.
Windows
macOS
Linux
Android
iOS
Plugin version
0.6.0
Additional context
Thank you for your help!
The text was updated successfully, but these errors were encountered:
The API does not offer a way to increase page size. Adding pagination to the search results in the plugin sounds like a lot of work. So this is not something I am going to tackle anytime soon, except if someone comes up with a good idea how to tackle this.
Describe the bug
it seems that pagination is not taking into account for the OMDB API. Example, when you search on "Seven", you only get a few results in the api but if you add the pagination, you get the next results.
Example: https://www.omdbapi.com/?s=Seven&apikey=[your_Api_Key]&page=4
To Reproduce
Search for Seven: you will only see a few results
Go on the url with your API Key and add &page=2 ... you will see the other results (for sure, depending on the search, there might be a lot of pages).
Expected behavior
Either a scroll or a pagination could be helpful because right now, some movies are missing.
Screenshots
Occurs on
Tested on Windows. No idea for the others but I guess the behaviour is the same.
Plugin version
0.6.0
Additional context
Thank you for your help!
The text was updated successfully, but these errors were encountered: