-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It is not taking into account Options #5
Comments
Hi,
The If you want to limit the number of posts that you want to show see Option's limit. Thanks for pointing out that I have to update the docs for v2. Will do these days. Let me know if this is clear enough. |
Hi π The limit of 10 only I gave you as an example. Having But if the page has about 5 thousand post this is no longer good. because you have to download a large amount of data and this becomes a very heavy That is why the post limit so that it can work well with a certain amount of data. Have a good day π |
Yeah, if you have 5000 posts the search will most likely break. So limit should be editable I guess. Another way to 'limit' could be to filter the posts that were published in the last 1-2 years. Depends on how regulary you post. I will make it editable in the next release. |
Now, in version 1.0.1 you can change the api parameters limit too. Keep in mind that if you change this value you might not get the same results as you should. If you have a small blog you can leave it to If you have a lot of posts you could change this value and set it to a number that makes sense. You could look at how many posts you published in the latest 2-3 years and perform the search only on those posts. Not ideal but better than a slow, very slow, search. Or you could use |
Thank you. You did a good job. |
Hi π
I realize there's a little problem
When you add options for the Api it is not taking into account.
β For example
As you can see, I only call 10 post, but It return all post and does not take into account any of these options that is added.
β Checking the code, I think I found the possible error.
ghost-search/src/ghost-search.js
Line 92 in e820cf8
This is solved by removing this line.
It is also necessary to update the documentation with the new values that the version two of the Api accepts.
The text was updated successfully, but these errors were encountered: