refactor and adopt google-maps-infobox into main package and create <InfoBox /> component about react-google-maps-api HOT 7 CLOSED

With OverlayView, why does anyone really need an InfoBox?

from react-google-maps-api.

https://github.com/tomchentw/react-google-maps/blob/master/src/components/addons/InfoBox.jsx

from react-google-maps-api.

@uriklar I have no idea, I think we can safely remove it.
What do you think about removing all add-on dependencies?

from react-google-maps-api.

I believe that InfoBox provides an easy way to have a popover style element that can have propagation stopped on it. This is useful for popovers that allow for user interaction.

I also personally think the options are much simpler for this use case versus trying to do all the same things with an OverlayView. For example here are some options i am using with react-google-maps and the popover:

{
  closeBoxURL: '',
  pane: 'floatPane',
  enableEventPropagation: true,
  alignBottom: true,
  maxWidth: 280,
  pixelOffset: new window.google.maps.Size(-140, 0),
  infoBoxClearance: new window.google.maps.Size(20, 20),
}

Again, much of this might be because I'm not as experienced setting up an OverlayView for this same use case (I've only used them for custom markers), but just my 2 cents.

from react-google-maps-api.

So what is the status on this issue? can we close it, or leave it be?

from react-google-maps-api.

update?

from react-google-maps-api.

I’m not currently working on it, so feel free to close it if you’d like.

from react-google-maps-api.