IT-Naturschutz/konova
7
0
Fork 0
Code Issues 6 Pull Requests 1 Actions Projects Releases 37 Wiki Activity

[Compensation] Conservation office #5

New Issue
Closed
opened 2021-08-26 12:54:24 +02:00 by mpeltriaux · 2 comments
mpeltriaux commented 2021-08-26 12:54:24 +02:00
Owner
Copy Link

Status quo

The compensation holds a conservation office inside responsible attribute.

Enhancement

Compensations inherit information about responsibilities from their related intervention's responsible attribute. Therefore, consider dropping the whole responsible attribute for Compensation model.

# Status quo The compensation holds a conservation office inside `responsible` attribute. # Enhancement Compensations inherit information about responsibilities from their related intervention's `responsible` attribute. Therefore, consider dropping the whole `responsible` attribute for `Compensation` model.
mpeltriaux added the
enhancement
 label 2021-08-26 12:54:24 +02:00
mpeltriaux self-assigned this 2021-08-26 12:54:24 +02:00
mpeltriaux commented 2021-08-30 09:45:53 +02:00
Author
Owner
Copy Link

responsible has not been dropped. responsible ist part of the AbstractCompensation which is the super class for Compensation and EcoAccount. EcoAccounts need the responsible attribute anyway, since they are not linked to any intervention directly. Refactoring responsible from AbstractCompensation into EcoAccount might backfire in the future, when laws can change and compensations would need the responsible attribute again.

We keep it where it is but do not use it for compensations (for now).
Instead, this branch holds a lot of enhancements regarding the KonovaCodes and their usage in the admin backend.

`responsible` has not been dropped. `responsible` ist part of the `AbstractCompensation` which is the super class for `Compensation` and `EcoAccount`. EcoAccounts need the `responsible` attribute anyway, since they are not linked to any intervention directly. Refactoring `responsible` from `AbstractCompensation` into `EcoAccount` might backfire in the future, when laws can change and compensations would need the `responsible` attribute again. We keep it where it is but do not use it for compensations (for now). Instead, this branch holds a lot of enhancements regarding the KonovaCodes and their usage in the admin backend.
mpeltriaux commented 2021-08-30 09:46:28 +02:00
Author
Owner
Copy Link

Merged by #15

# Merged by #15
Sign in to join this conversation.
5_compensation_conservation_office
Branches Tags
Labels
Clear labels
backlog
Absolutely no priority, but maybe some day...
bug
Something is not working
duplicate
This issue or pull request already exists
enhancement
Idea for existing feature
feature
New feature
help wanted
Need some help
invalid
Something is wrong
question
More information is needed
wontfix
This won't be fixed
bug
Something is not working
duplicate
This issue or pull request already exists
enhancement
New feature
help wanted
Need some help
in discussion
invalid
Something is wrong
MAUS - Pacht
Issues für Maus-Pacht / Version processware
priority
1
priority
2
priority
3
priority
4
priority
5
question
More information is needed
wontfix
This won't be fixed
No Label
enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
btuelek jhaeder mmannfeld mmueller mpeltriaux sgorell srieder tnette
No Assignees mpeltriaux
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: IT-Naturschutz/konova#5
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?