Closed oesukam closed 4 years ago
@knowbee Thanks for the feedback. I just updated it to develop
.
@knowbee Thanks for the feedback. I just updated it to
develop
.
You can also rename you branch to ft-refactor-data-file or feature-refactor-data-file so that future pull requests follow the same format. Thanks
@knowbee I think ft
or feature
would more make sens if it was about adding a new feature but this PR doesn't change the current implementation but only refactor the codebase. We can maybe have feature
(New feature), refactor
(Refactor the codebase), bug
(fixing bug), chore
(improving the development environment)
@knowbee I think
ft
orfeature
would more make sens if it was about adding a new feature but this PR doesn't change the current implementation but only refactor the codebase. We can maybe havefeature
(New feature),refactor
(Refactor the codebase),bug
(fixing bug),chore
(improving the development environment)
sounds about right ๐, update accordingly.
@knowbee I think
ft
orfeature
would more make sens if it was about adding a new feature but this PR doesn't change the current implementation but only refactor the codebase. We can maybe havefeature
(New feature),refactor
(Refactor the codebase),bug
(fixing bug),chore
(improving the development environment)sounds about right ๐, update accordingly.
I have updated contributing guideline with your naming convention suggestion. check it out
@knowbee Under Branch naming
, instead of Summary
, I think it should be Example
as refactor-data-file
@knowbee If possible to also add the link to the contribution guideline in the readme for easy access
What does this PR do?
This PR puts provinces, districts and sectors into different files in order to improve the code maintainability
How to test?
console.log(Provinces()); // [ 'East', 'Kigali', 'North', 'South', 'West' ] console.log(Districts()); // [ 'Bugesera', 'Gatsibo', 'Kayonza', 'Kirehe',...]