We are looking for an active maintainers and or someone to take the "bull by the horns" on the project. @nmccready is active on other projects right now and does not have the time to dedicate to this project as needed. Therefore we are looking for some developers who would like to take the lead on this project. It is totally ripe for a rewrite (3.0, and angular 2.0). Email or private msg (gitter) nmccready if interested.

AngularJS directives for Google Maps

For Pull Requests please see branching scheme below! Realize that PRS to master are for 2.1.X only. If you want it rolled into a 2.0.X release PR to 2.0.X.

Master (2.1.X): 2.1.X: 2.0.X:

task board:

This is a set of directives and services for AngularJS ~1.0.7+, ^1.2.2+.

If you plan to hack on the directives or want to run the example, first thing to do is to install NPM dependencies:

npm install #note bower install is run on post install 

• Installing for Meteor application:

meteor add angularui:angular-google-maps

To build the library after you made changes, simply run grunt:

grunt

If you get errors from jshint or specs, just add the --force argument.

grunt mappAll

This will generate source maps for development (angular-google-maps_dev_mapped.js) (non minified) and source maps to minified (angular-google-maps_dev_mapped.min.js) files. They each have their own corresponding map files. To get the coinciding source files you will need to copy the generated /tmp directory (currently not under scc).

To run the example page, just run

grunt example

and open your browser on http://localhost:3000/example.html.

The various directives are documented at official site.

Filing issues: Prior to submiting an issue:

• Search open/closed issues, src examples (./examples), gitter, and then google plus community! Again please search!
• issues w/ plnkrs get attention quicker

Pull requests more than welcome! If you're adding new features, it would be appreciated if you would provide some docs about the feature. This can be done either by adding a card to our Waffle.io board, forking the website branch and issuing a PR with the updated documentation page, or by opening an issue for us to add the documentation to the site.

• master: points to the active targeted next release branch (2.1.X)
• 2.0.X: latest of 2.0.X
• 2.1.X: "" ... etc