loogle
loogle copied to clipboard
Add ?limit= parameter
This fixes #40.
This would fix #40, but only in a rather superficial way: The hits are still generated, just not returned to the client. I wonder how useful that is.
I’d suggest we don’t merge this yet, but wait until I had time to refactor the code to pass the parameter through to the backend (or merge backend and frontend). Until then, @oOo0oOo, I suggest that your client passes the limit attribute (it will be ignored for now), but also applies the limit client side. How does that sound?
Absolutely, I would welcome a proper implementation. There is no urgency on my end, I'll make my changes when this is released.