Skip to content

Conversation

@ketanreliefapps
Copy link
Contributor

@ketanreliefapps ketanreliefapps commented Mar 9, 2023

Description

in the main GIS front-end branch, we define a few methods to generate random GeoJSON
Put that in the back-end, we should put some new utils methods, that would allow GeoJSON to be randomly generated
Purpose is to be able, short term, to have rest endpoint we would use to consume data in the front-end

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Improvement (refactor or addition to existing functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

this code is only for backend, so you are don't able to test currently

Checklist:

  • * My code follows the style guidelines of this project
  • * Linting does not generate new warnings
  • * I have performed a self-review of my own code
  • * I have commented my code, particularly in hard-to-understand areas
  • * I have put JSDoc comment in all required places
  • * My changes generate no new warnings
  • * I have included screenshots describing my changes if relevant
  • * I have selected labels in the Pull Request, according to the changes with code brings
  • I have made corresponding changes to the documentation ( if required )
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

@AntoineRelief AntoineRelief merged commit 6dc355a into feat/AB#16229_GIS Mar 9, 2023
@AntoineRelief AntoineRelief deleted the feat/AB#58618_Move_all_GIS_random_generation_to_the_back_end branch March 9, 2023 12:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants