Name: angular-google-maps
Owner: AngularUI
Description: AngularJS directives for the Google Maps Javascript API
Created: 2012-08-16 12:50:47.0
Updated: 2018-01-17 16:29:06.0
Pushed: 2017-05-17 11:41:22.0
Homepage: http://angular-ui.github.io/angular-google-maps
Size: 95495
Language: CoffeeScript
GitHub Committers
User | Most Recent Commit | # Commits |
---|
Other Committers
User | Most Recent Commit | # Commits |
---|
With angular 2 and other competing projects we have decided to announce that this project is no longer activley maintained. If someone desires to take over the project please contact any of the admins.
As a warning this project is not activley watched by the admins and is checked here and there to fix any major issues. Therefore if something is major, contact someone directly via mentioning a users name/alias (will notify the user/admin).
Alternatives:
Builds:
This is a set of directives and services for AngularJS ~1.0.7+, ^1.2.2+
.
Please always be checking the package.json and bower.json. They are the spoken word and will usually be more up to date than this readme.
Tip use some library which will always pull in your dependencies (no matter what the changes are) to your vendor.js. IE: main-bower-files
Current Dependencies:
If you plan to hack on the directives or want to run the example, first thing to do is to install NPM dependencies:
install && bower install
or add angularui:angular-google-maps
or npm install --save angular-google-maps
To build the library after you made changes, simply run grunt:
t
If you get errors from jshint
or specs, just add the --force
argument.
t buildAll
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
t example
and open your browser on http://localhost:3000/example.html
.
The various directives are documented at official site.
Filing issues: Prior to submitting an issue:
Pull Requests (PR) 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.
PR's should follow angular git commit conventions.
PRS to master are for 2.3.X only.
If you want it rolled into a older release then target your PR to that respective branching name like 2.1.X.
Note: many fixes relevant to 2.0.X can be rolled up into 2.1.X, 2.2.X and 2.3.X