Existing example does not really tell how/where to implement the code
What kind of change does this PR introduce? (check at least one)
[ ] Bugfix
[ ] Feature
[ ] Code style update
[/] Provided documentation update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:
Does this PR introduce a breaking change? (check one)
[ ] Yes
[/] No
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
[ ] It's submitted to the dev branch and not the master branch
[ ] When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
[ ] It's been tested with all major browsers
If adding a new feature, the PR's description includes:
[ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)
Other information:
Just updating documentation with more useful example
rstoenescu
commented
6 years ago
Existing example does not really tell how/where to implement the code
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
devbranch and not themasterbranchfix: #xxx[,#xxx], where "xxx" is the issue number)If adding a new feature, the PR's description includes:
Other information:
Just updating documentation with more useful example