Closed
Description
Use Case
See PIN 16 (PR #2134) for background. This is a spin-off from #2141 for only one (special) handler, ConstantResultHandler
, which has internal implications.
Solution
Implement a Result
subclass for ConstantResultHandler
that knows how to .read
, write
, and check if it .exists
and operates properly for the same internal purposes as the current ConstantResultHandler
does.
Alternatives
Please describe any alternatives you've considered, even if you've dismissed them
Activity