Esri welcomes contributions from anyone and everyone. Please see our guidelines for contributing.
There are many ways you can contribute to the ArcGIS Flex API Samples.
- Suggest enhancements on forum or as GitHub issues.
- Report potential bugs to Esri Support.
- Contribute code, as pull requests, to the ArcGIS Flex API samples.
This guide describes how you can contribute code improvements to the ArcGIS Flex API samples.
- Make sure you have a GitHub account.
- Fork the Flex API Samples repo on GitHub.
- Clone it to your local machine.
- Checkout the develop branch.
- Create a new feature branch on your local machine.
- The name of the branch doesn't matter, but as a best practice use a descriptive name like "add-errorcheck-for-annotation-layers".
- Write code to add an enhancement or fix the problem.
- Follow the coding conventions already used in the samples (spaces instead of tabs, proper indentation, use Flex Formatter along with our Flex Formatter settings).
- Document your code.
- Make commits of logical units.
- Use clear and descriptive commit messages.
- Test your code.
- Push the changes in your feature branch to your repo.
- Submit a pull request against the "develop" branch. Submitting a pull request will open a GitHub issue.
- Clearly describe the issue including steps to reproduce; or if an enhancement, indicate the functionality you built.
By contributing your code, you agree to license your contribution under the terms of the Apache License 2.0. See item 5 of /~https://github.com/Esri/arcgis-viewer-flex/blob/master/license.txt for more details.