Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • Possible duplicate of Choosing the right Design Pattern Commented Jun 2, 2017 at 11:01
  • A common interface should not lead to any violations of Liskov substitution principle as long as you implement it in a consistent manner. What's wrong with throwing an exception and letting the calling code deal with it? Commented Jun 2, 2017 at 11:14
  • 1
    I am currently working on producing a library that solves the same or a very similar problem. See this question for a breakdown of the patterns I used. Commented Jun 5, 2017 at 19:24