Incorrect results if not specifying nativeGeo when the redis server supports native geo command

Hi,

I am using redis server 3.2.3 which supports native geo command. I found that if I call nearby() function with the following options, the results will be very limited (I guess the unit used isn’t correct)

{
  withCoordinates: true,
  withDistances: true,
  units: 'mi',
  accurate: true
}

My peer uses old redis server (3.0.7), it works fine with the same code. Then I tried to append nativeGeo: true on initialization, everything goes well. But my server doesn’t support native geo command, it will be great and better let the lib determine whether to use native command.

Thanks :]

[arjunmehta]

@seoker I’ve address this in the latest release, 3.1.1.

Published to npm. I went with option 2 from above. A command queue is created and drained upon detection of the right interface.

[arjunmehta]

This makes sense. I’m realizing this is a major bug and it’s not an easy problem to solve, but there are two things I can do:

1. The easiest thing to do would be to have a ready or initialized event. That can be used to know when to start using the module. Not the most intuitive or convenient solution.
2. More time consuming to do would be to have a queue that is drained on initialization with the right interface. This would be invisible and seamless. This would take some time to develop and test, but is the ideal solution (in my opinion).

Anyway, I’ll give it a go soon.

Thanks!