Fix grid max zoom

[vicb]

The grid also skip clustering if >= maxZoom

js-markerclusterer/src/algorithms/grid.ts

Line 76 in 1193ff4

if (map.getZoom() >= this.maxZoom) {

We the comparison should be >= instead of >

Some other minor cleanups

Notes:

• I documented/changed the code base on the implementation of the grid algo. We could also decided that maxZoom should be excluded but it would change the behavior of the grid algo
• Interestingly I figured that the supercluster does nothing with the max zoom... looks like a bug to me (and already reported as SuperClusterAlgorithm keeps displaying cluster at maximum zoom level #647) edit: it's actually an option of the SuperCluster

[vicb]

Note that SuperCluster defines maxZoom as "Maximum zoom level at which clusters are generated."

This is not what is implemented in this CL (ref "We could also decided that maxZoom should be excluded but it would change the behavior of the grid algo" in the initial description).

So first step would be to decide and document what the desired behavior is and then make the corresponding updates in gris/supercluster.

[wangela]

Thanks for contributing this fix, @vicb!

[googlemaps-bot]

🎉 This PR is included in version 2.3.1 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)
• v2.3.1

Your semantic-release bot 📦🚀

[vicb]

@wangela I don't think this should have been merged without resolving the open question in the description and comment - that is grid and clusterer should be consistent.

[wangela]

@vicb Oops, I missed that in the discussion. Perhaps we should keep PRs in "Draft" state until disussion points are all resolved.

[vicb]

I didn't know draft PRs were a thing but yeah that and reading PRs description/comments/notifications would help.
We'll do better next time ;)

Any thoughts on the question?