Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix planning area assignment #352

Merged
merged 1 commit into from
Jul 27, 2021
Merged

Conversation

Dyostiq
Copy link
Contributor

@Dyostiq Dyostiq commented Jul 20, 2021

Substitute this line for a meaningful title for your changes

Overview

Please write a description. If the PR is hard to understand, provide a quick explanation of the code.

Designs

Link to the related design prototypes (if applicable)

Testing instructions

Please explain how to test the PR: ID of a dataset, steps to reach the feature, etc.

Feature relevant tickets

Link to the related task manager tickets


Checklist before submitting

  • Meaningful commits and code rebased on develop.
  • If this PR adds feature that should be tested for regressions when
    deploying to staging/production, please add brief testing instructions
    to the deploy checklist (docs/deployment-checklist.md)
  • Update CHANGELOG file

@vercel
Copy link

vercel bot commented Jul 20, 2021

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployments, click below or on the icon next to each commit.

marxan – ./app

🔍 Inspect: https://vercel.com/vizzuality1/marxan/3oQGQ2UVzmpUUJnM1wJxVxJqcteZ
✅ Preview: https://marxan-git-fix-planning-area-assigning-vizzuality1.vercel.app

marxan-storybook – ./app

🔍 Inspect: https://vercel.com/vizzuality1/marxan-storybook/FaFchfpQQxvN4dpXk5SNeGcNAvPd
✅ Preview: https://marxan-storybook-git-fix-planning-area-assigning-vizzuality1.vercel.app

@Dyostiq Dyostiq marked this pull request as ready for review July 21, 2021 19:17
@Dyostiq Dyostiq requested a review from kgajowy July 21, 2021 19:17
@@ -136,6 +136,7 @@ export class ProjectsCrudService extends AppBaseService<
*/
const project = await super.setDataCreate(create, info);
project.createdBy = info?.authenticatedUser?.id!;
project.planningAreaGeometryId = create.planningAreaId;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🙈 is geometry the same as area?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't want to change the api contract, and it looked like setting planningAreaId is used to set a custom planning area, whereas planningAreaId is a generic calculated field in the entity, and planningAreaGeometryId is a actual column in the entity representing the assigned custom planning area

@Dyostiq Dyostiq merged commit 03c22b2 into develop Jul 27, 2021
@Dyostiq Dyostiq deleted the fix/planning-area-assigning branch July 27, 2021 13:33
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.

2 participants