Discussion of various forks

[devinrhode2]

If you compare the npm version between react-bingmaps and https://www.npmjs.com/package/react-bingmaps-plus, you'll see react-bingmaps has stopped receiving updates 2 years ago, and react-bingmaps-plus has started receiving updates.

[devinrhode2]

Sorry, looks like this form from m. chuang is for adding clustering support. I will comment here if there's other interesting changes.

[devinrhode2]

Looks like @hanzlamateen's fork is the successor to m. chuang's react-bingmaps-plus - furthermore, it's renamed to react-bingmaps-vnext - located here: https://github.com/hanzlamateen/react-bingmaps All changes here: dev...hanzlamateen:dev

mojotech's fork adds support for polylines/related stuff

DSilence's fork, I'm not sure, some stuff with irregular polygons. @DSilence - care to share a summary of your fork? dev...DSilence:dev
Looks like @send2moran's fork also does something with irregular polygons: dev...send2moran:dev

Some other forks have some small features that I am not interested in (creating a very simple store locator page with a list of stores to the left of the map, no clustering, etc)

@hanzlamateen - would you generally recommend your fork over this main project?

I believe our company's team will build our own wrapper for react closed-source :(

Unfortunately this component doesn't even use jsx, I'm curious... does anyone knows about any react bing maps wrapper that is better than this one?

2 major user-facing issues I have with this component are:

1. Pins flicker down and to the right whenever we select a different store (either clicking a map pin, or clicking a different store in our list on the left)
2. Changing props that are passed to the map can't be updated in a typical react fashion. (Changing disableScrollWheelZoom map option doesn't affect the map #38)

[devinrhode2]

This is also a major issue - getting a reference to the map instance: #36