This repository has been archived by the owner on Feb 19, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #416 from onaio/staging
v1.3.3 Release
- Loading branch information
Showing
12 changed files
with
358 additions
and
381 deletions.
There are no files selected for viewing
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,51 @@ | ||
# Contributing to Gisida | ||
|
||
The following is a set of guidelines for contributing to Gisida. Changes to this document can be proposed via a pull request. | ||
|
||
### Table of contents | ||
|
||
[Branch naming](#branch-naming) | ||
|
||
[Creating an issue](#creating-an-issue) | ||
|
||
[Don't](#dont) | ||
|
||
## Branch naming | ||
|
||
A branch is named by separating various parts with a forward slash. The structure of a branch name is as follows | ||
|
||
`group-token/issue-number_awesome-branch-name` | ||
|
||
e.g **feature/300_layer-builder** | ||
|
||
The following are tokens that can be used and their meaning: | ||
|
||
**bug**: Malfunctions that should be fixed to comply with the expected behaviour | ||
|
||
**enhancement**: Improvement of an existing feature | ||
|
||
**feature**: A new feature | ||
|
||
## Creating an issue | ||
|
||
### Before creating an issue | ||
|
||
- Use the search feature to make sure there issue doesn’t already exist. If this does happen though, close the less thorough issue and include a comment e.g **Duplicate of #123** | ||
|
||
### How do I create a good issue? | ||
|
||
- Keep the titles short and descriptive. Have the specific details in the issue descripion. | ||
|
||
- Avoid issues that contain too much detail. Split a complex issue. | ||
|
||
- Mention relevant people _@username_ if necessary. | ||
|
||
- Add information that can help clarify the issue e.g screenshots of Javascript errors and warnings. | ||
|
||
- In case of a bug, give as details as possible of how to reproduce the bug and the expected behaviour. | ||
|
||
## Don't Do | ||
|
||
- Don't create a merge request if your source branch has commented out code. | ||
|
||
- Don't use long and descriptive names when creating issues and pull requests. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,37 @@ | ||
# Labels | ||
|
||
## Show zeros | ||
|
||
Some situations may require that 0 values be rendered on the map while others may require the 0 values to be omitted. | ||
The default behaviour is that 0s are rendered. If you do not want 0 values to render for a certain layer, update the layer configuration as | ||
|
||
``` | ||
{ | ||
... | ||
"labels": { | ||
... | ||
"showZeros": false | ||
... | ||
} | ||
... | ||
} | ||
``` | ||
|
||
The fill color needs to be set to white for 0 limit so that it provides the illusion of no data rendered. If you choose to have another color other than white, the fill will render on the map but will have no value associated with it. | ||
|
||
Here is an example: | ||
|
||
``` | ||
{ | ||
... | ||
"categories": { | ||
... | ||
"color": ["#ffffff","#c7e9c0","#a1d99b","#74c476","#31a354","#006d2c" | ||
], | ||
"limit": [0,13,32,52,61,100], | ||
} | ||
... | ||
} | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.