Hi thank you, fully agree. Will check PR later today or tomorrow.

All is fine, may be add ability to use NE SW (if NW SE is not provided) to documented fitBounds ?

@istarkov It's make sense, what do you think about such approach:

1. If we have NW and SE we're just using them.
2. If we have NE and SW we're converting them into NW and SE and using same algorithm that we have in fitBounds method.

Super!

@istarkov cool, i'll push changes tomorrow morning

Thank you!

@istarkov hm, I thought a little bit about it today, and i don't really like that we're passing NE and SW to fitBounds, but it returns NW and SE. What do you think about it?

Also i think will can add some helpers like convertNeSwToNwSe and convertNwSeToNeSw, cause we're repeating this logic in few places.

Agree that newBounds must have all corners,
any your decision on convertXXX2YYY will be good.

@istarkov done!

Super,
from first days I had knowledge that bounds object is not similar to others API
(and my laziness didn't allow me to fix that)

all that my

  const ne = { lat: nw.lat, lng: se.lng };
  const sw = { lat: se.lat, lng: nw.lng };
  return new LatLngBounds(sw, ne);

now will gone ;-)

Thank you a lot!!!!

At npm [email protected]

Cool, glad that i helped 😉

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.