Thomas Heartman 8337885e47 feat: return CR uses of segments when flag is active (#5378) ... This PR changes the payload of the strategiesBySegment endpoint when the flag is active. In addition to returning just the strategies, the object will also contain a new property, called `changeRequestStrategies` containing the strategies that are used in change requests. This PR does not update the schema. That can be done later when the changes go into beta. This also allows us some time to iterate on the payload without changing the public API. ## Discussion points: Should `strategies` and `changeRequestStrategies` ever contain duplicates? Take this scenario: - Strategy S uses segment T. - There is an open change request that updates the list of segments for S to T and a new segment U. - In this case, strategy S would show up both in `strategies` _and_ in `changeRequestStrategies`. We have two options: 1. Filter the list of change request strategies, so that they don't contain any duplicates (this is currently how it's implemented) 2. Ignore the duplicates and just send both lists as is. We're doing option 2 for now.		2023-11-22 07:51:04 +01:00
..
segment-service-interface.ts	feat: return CR uses of segments when flag is active (#5378)	2023-11-22 07:51:04 +01:00