...
ACTIONS RDW make these things so. STATUS: Work will be tracked under case idp-287.complete r4543 r4543
AttributeRule
Have we make this an interface and have Permit and Deny variants? There are three options
...
ACTION RDW: look at each of these in the code (both implementation and parsing) and circulate the results. STATUS complete.
Matcher
Scott still unhappy with the shoe-horning of “once class two jobs”. STATUS see the updated design notes
We need to ensure that unmodifiable returns are (and the static ones are not). ACTION RDW do so or JIRASTATUS: complete r4544
AbstractComparisonMatcher
Does this become easier once we separate the two roles? Then we can get rid of the injected inline predicates. Predicate is looking like an increasingly uncomfortable match for the comparison. Answer: RDW thinks so. He needs to complete my other actions and then play with this. STATUS new design thrashed out and is now in The design notes