Actions
Architecture #3557
closed
Refactoring in Workflows
Status:
Rejected
Priority:
3
Assignee:
-
Category:
Architecture - Code maintenance
Target version:
Pull Request:
Effort required:
Name check:
Fix check:
Regression:
No
Description
Now that workflows are more or less stabillized, we have a far better view about what we need and what should desapear.
Some requirement not fulfullid:
- "workflow enabled" properties should be use at one point only
- in [WR]oChangeRequestJdbcRepository, we should not use Try to immediatly test for success
- we don't want to use Box.Empty
- in other data access layer, logs are done in the repository, not in the service. We should do the same here.
Updated by Nicolas PERRON over 11 years ago
- Target version changed from 2.7.0~beta1 to 2.7.0~rc1
Updated by Nicolas PERRON over 11 years ago
- Target version changed from 2.7.0~rc1 to Ideas (not version specific)
Updated by
Updated by François ARMAND about 1 year ago
- Status changed from New to Rejected
- Regression set to No
This is not relevant anymore, code changed a lot since then.
Actions