Benoît Bouré

Any update on this? I am getting errors due to `IncludeBody` being true for on-supported events. This PR would fix the issue. Thanks

I'd like to back this PR, although I would move the session params at the Query level (instead of the Connection level). That leaves you more flexibility to choose not...

Thanks for your feedback @missinglink That sounds great. Looks like a big refactoring though. How about turning the importers into a "service", with a modulable API. Then, one could do...

Sorry if this wasn't clear. Let me clarify, and simplify. We could change the `import` function to accept an array of functions (the middlewares I was talking about). `importPipeline` could...

Thanks for your feedback @missinglink I don't see cons in extending `/reverse` and `/nearby`. I also thought about it, but then I thought that it was a slightly different concept...

@missinglink > Changing the point param to optional would be a breaking change to the API and so might cause some friction. If we could leave this unchanged it would...

Thanks @Joxit for your feedback. > We should probably also add categories with this :) (all shops in this bbox, bus stations in this bbox...) Yeah, this is in fact...

> How about we start there and once that's done we take another look at reverse? Sounds good. I am willing to try and open a PR about this soon....

> One thing to be aware of there is pelias/api:sanitizer/nearby.js@master#L15 , this line uses the same point sanitizer as reverse, which generates an artificial boundary.circle around the point when one...

> What you're proposing is to (at some scales, like zoomed out to see the whole world) have every record matched in the 'hits' (which can be >500,000,000) and then...