-
Notifications
You must be signed in to change notification settings - Fork 5
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
feat(api): scenario planning units: integrity rule #224
feat(api): scenario planning units: integrity rule #224
Conversation
This pull request is being automatically deployed with Vercel (learn more). marxan – ./app🔍 Inspect: https://vercel.com/vizzuality1/marxan/5yD2EgxTEpivZinbzBrS5pQpmSQb marxan-storybook – ./app🔍 Inspect: https://vercel.com/vizzuality1/marxan-storybook/7Gt2cpYHyd2kdrhVXakeKReCVikQ |
api/libs/scenarios-planning-unit/src/domain/lock-planning-units.ts
Outdated
Show resolved
Hide resolved
api/libs/scenarios-planning-unit/src/domain/lock-planning-units.ts
Outdated
Show resolved
Hide resolved
api/libs/scenarios-planning-unit/src/domain/lock-planning-units.ts
Outdated
Show resolved
Hide resolved
api/libs/scenarios-planning-unit/src/domain/lock-planning-units.spec.ts
Outdated
Show resolved
Hide resolved
* feat(geoprocessing): scenario planning units: use integrity rule * refactor: rebase and adjust to domain change * chore: rename framework-specific adapter to just repository * chore: rename cost surface internals
This rule will be used by both API and Geoprocessing when updating PU lock status.
Recommended review order: