@alexandregiordanelli If you do have an issue with how the library performs I invite you to open a pull request with suggested changes, rather than just personal attacks towards me.

Now in regards to some points you mention:

• Yes this is effectively a port of Geofire for Firestore, I've been pretty open with that.
• You are able to perform where filters using the library as one of the arguments for your query object is a query function, so that's not really an issue. But I think you're referencing using where for the instead of startAt and endAt, which I think may be a good idea. I think it'll offer a similar performance, as its still a ranged query, however it'll open up the orderBy query modifiers for use by devs.

Point is I like your idea, but I do not appreciate the manner you expressed yourself and will ask that you try to be more courteous moving forward. Otherwise I will just close the issue and block you.

Sorry man! I didnt see the startAt and endAt filter.. I think you are right. I edited my issue and remove bad words.. Really sorry.. It is sad firestore doesnt have native geoqueries. thanks for share yor thoughts

Thank you for the apology @alexandregiordanelli , and I'm sorry if I came off a little strong. Anyway, I took your suggestion of using the where instead of my startAt and endAt. While I may not be able to do more with it now, I think it's the right solution for the library down the road.