Community
Participate
Working Groups
In order to provide a better user experience, it would be nice if the explanation was able to return in one shot all the information about missing requirements. The test case ExplanationTest shows such an example. However we need to be careful to see if this will end up returning false positive.
I guess we could simply collect all the missing requirements and return them if any. Note that in that case we would not have a real explanation, i.e. we would not get the path from the request to the missing requirements, only the missing reqs. Else we could compute a real explanation.
When you say we could collect all the missing requirements. How would that differ from what we have in Slicer? If we do something in that space, and if at all possible, I think we should strive to compute a real explanation.
I was thinking about the #missingRequirement() method in the projector. The problem with real explanations, is that we need to return a set of explanations instead of a single explanation currently, which will probably break the API.
