Map events in general about angular-google-maps HOT 2 CLOSED

There's a few events that aren't yet covered and am wondering which ones you plan to target? Should we attach to all of the events on here? I'm sure they'd all eventually get requested:

@intellix yeah I fully agree on this: we definitely have to support all the available events.

Currently, there is no way to detect if the developer uses a certain EventEmitter, so I don't see any other way to attach event listeners for all events atm.

Some things to note for implementing new events:

• On MarkerManager level, some refactoring is needed here:
  marker-manager.ts#L44
  It is not a good way to create a separate method for every event. I did this already for the SebmGoogleMap Component (on Map level) here: google-maps-api-wrapper.ts#L48 - So something similar is needed for the Marker before adding new event listeners.
• New EventEmitter names should be named in present tense and camel cased:
  Native Google Maps API Event: maptypeid_changed -> EventEmitter name: mapTypeIdChange
• When there is a native browser event for a Google Maps API Event (for example click), it should get prefixed (to not bind to a native browser event): click -> markerClick
• For mouse events, we should introduce a new Interface that gets used in Map and Marker Events that are related to mouse events. (There is a MapMouseEvent interface at the moment, but the same interface could also get used in markers: MapMouseEvent

I can PR some of these, but just want to know what you think about it first as you didn't do them yet so maybe have a reason for not including (performance?)

Would be awesome! 😎 Also, I'm happy to discuss all these things I described here.

from angular-google-maps.

Already resolved

from angular-google-maps.