Pattern idea: Opaque state machine about elm-patterns HOT 1 OPEN

Thanks.
Looking at your example I realised that this is a pattern we use often.

In our case it just grew organically because of the need to have things that have:

• can be treated as one thing (Entity)
• have a common part (the GenericInternals in both) and a specific part (the id)

Don't know how to name it, and unsure this needs to be a named pattern.

If we want to make this a named pattern I think we need to:

• Explain the problem in a simpler way, I think I would not mention the other patterns, just what we are trying to achieve
• Find a good name for it

from elm-patterns.