as @joshzamor recommend I was about to use feature flag in performance task for supply lines but I’ve encountered one issue. Most of the work for this ticket will be adding REST expand the feature to Supply Lines which will require a complete rework of DTO classes connected with this resource. If we want to preserve old code to use feature flag then 2 separate DTO classes for Supply Lines are needed which then causes complication in the controller method:
- we need to return 2 different classes so we probably need to use ResponseEntity<?> which causes sonar issues
- for a lifetime of feature flag, rest-api validation must handle both responses
I’m not sure if using feature flag for this case is the way to go. What do you guys think?