-
Notifications
You must be signed in to change notification settings - Fork 20
Open
Labels
part:❓We need to figure out which part is affectedWe need to figure out which part is affectedpriority:❓We need to figure out how soon this should be addressedWe need to figure out how soon this should be addressedtype:enhancementNew feature or enhancement visitble to usersNew feature or enhancement visitble to users
Milestone
Description
What's needed?
Currently, when there are simultaneous requests for not matching but overlapping sets of components, we'll get an error. This should change.
Proposed solution
When there are ovelapping component ids in 2 requests, they need to be broken down in to 3 separate buckets, one with the common components and one with the unique component ids for each request, and target powers should be calculated for each of them separately.
Use cases
No response
Alternatives and workarounds
No response
Additional context
No response
Metadata
Metadata
Assignees
Labels
part:❓We need to figure out which part is affectedWe need to figure out which part is affectedpriority:❓We need to figure out how soon this should be addressedWe need to figure out how soon this should be addressedtype:enhancementNew feature or enhancement visitble to usersNew feature or enhancement visitble to users
Type
Projects
Status
To do