[api] fixes csv features upload to save features as is_legacy=true for correct puvspr.dat generation [MRXN23-279] #1421
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.
Fix saving features uploaded with cs file
Overview
Small fix that sets new features, uploaded with csv file, to have value
is_legacy=true
. After csv feature upload project sources has already been being set tolegacy_import
. Setting features as legacy was missing for correct data generation made byPuvsprDatLegacyProject.getAmountPerPlanningUnitAndFeature()
Designs
Link to the related design prototypes (if applicable)
Testing instructions
Upload features from csv file to a projects scenario. New features must have
is_legacy=true
in (apiDB).featuresTable.Generating puvspr.dat file must return amounts per species per planning units in accordance with csv file data (not an empty table as it is now).
Feature relevant tickets
Link to the related task manager tickets
Checklist before submitting
develop
.deploying to staging/production, please add brief testing instructions
to the deploy checklist (
docs/deployment-checklist.md
)