Skip to content
This repository has been archived by the owner on Oct 6, 2023. It is now read-only.

Latest commit

 

History

History
33 lines (19 loc) · 2.26 KB

CONTRIBUTING.md

File metadata and controls

33 lines (19 loc) · 2.26 KB
Raw

Esri welcomes contributions from anyone and everyone. Please see our guidelines for contributing.

Before filing an issue

Please take a look at previous issues that resolve common problems.

If you're just looking for help, you'll probably attract the most eyes if you post in GIS Stackexchange or the Esri Leaflet place on GeoNet.

If you think you're encountering a new bug, please feel free to log an issue and include the steps to reproduce the problem (and preferably a running sample).

I want to contribute, what should I work on?

There is a lot of room for contributions to Esri Leaflet and Esri Leaflet Renderers. Make sure you checkout the development instructions in the readme to help you get started.

More examples

The Esri Leaflet website is written using http://assemble.io/ and can be found at https://github.com/Esri/esri-leaflet/tree/master/site/source. You can use the existing examples as a reference.

Setting up a dev environment

  1. Fork and clone Esri Leaflet Renderers
  2. cd into the esri-leaflet-renderers folder
  3. Install the dependencies with npm install
  4. run grunt from the command line. This will start the web server locally at http://localhost:8001 and start watching the source files and running linting and testing commands.
  5. Make your changes and create a pull request

Linting

Please make sure your changes pass JS Hint. This will help make sure code is consistent throughout Esri Leaflet. You can run JS Hint with grunt jshint.

Testing

Please make sure your changes dont break existing tests. Testing is essential for determining backward compatibility and catching breaking changes. You can run tests with grunt karma:run, grunt karma:watch or grunt karma:coverage.