link scenarios correctly to cost surfaces after cloning [MRXN23-606] #1661
Conversation
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
hotzevzl
changed the base branch from
develop
to
fix/api/MRXN23-599_export-and-import-lock-status-set-by-user-flag
hotzevzl
force-pushed
the
fix/api/MRXN23-606_link-scenarios-correctly-to-cost-surfaces-after-cloning
branch
from
6c95829 to
2e1137e
Compare
hotzevzl
force-pushed
the
fix/api/MRXN23-606_link-scenarios-correctly-to-cost-surfaces-after-cloning
branch
from
5cfc3e4 to
ade6c54
Compare
KevSanchez
reviewed
Mar 11, 2024
api/apps/geoprocessing/src/import/pieces-importers/project-cost-surfaces.piece-importer.ts
Outdated
Show resolved
Hide resolved
KevSanchez
approved these changes
Mar 11, 2024
hotzevzl
force-pushed
the
fix/api/MRXN23-606_link-scenarios-correctly-to-cost-surfaces-after-cloning
branch
from
ade6c54 to
8b6cfa4
Compare
hotzevzl
force-pushed
the
fix/api/MRXN23-606_link-scenarios-correctly-to-cost-surfaces-after-cloning
branch
from
8b6cfa4 to
e83d591
Compare
Base automatically changed from
fix/api/MRXN23-599_export-and-import-lock-status-set-by-user-flag
to
develop
March 11, 2024 13:05
hotzevzl
force-pushed
the
fix/api/MRXN23-606_link-scenarios-correctly-to-cost-surfaces-after-cloning
branch
from
e83d591 to
881a27f
Compare
|
another yolo merge, pending hexagonization of one method to use a mock in tests instead |
hotzevzl
deleted the
fix/api/MRXN23-606_link-scenarios-correctly-to-cost-surfaces-after-cloning
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allow scenarios to be linked correctly to copies of cost surfaces within cloned projects.
Feature relevant tickets
https://vizzuality.atlassian.net/browse/MRXN23-606
Checklist before submitting
develop.deploying to staging/production, please add brief testing instructions
to the deploy checklist (
docs/deployment-checklist.md)