Stylianos Gakis
04/04/2023, 12:46 PMbod
04/04/2023, 12:50 PMStylianos Gakis
04/04/2023, 1:22 PMFlow
and then we had a bunch of types implementing it, like
TerminationDateFlow
, TerminationLocationFlow
, and then others of another concept, like ClaimDateFlow
, ClaimLocationFlow
so I was looking if we can make a subtype of type TerminationFlow
and ClaimFlow
so that these other types can extend from instead so have a bit better story in how we handle these generated types.
now:
interface Flow
type TerminationDateFlow implements Flow { ... }
type TerminationLocationFlow implements Flow { ... }
type ClaimDateFlow implements Flow { ... }
type ClaimLocationFlow implements Flow { ... }
potential future:
interface Flow
interface TerminationFlow implements Flow
interface ClaimFlow implements Flow
type TerminationDateFlow implements TerminationFlow { ... }
type TerminationLocationFlow implements TerminationFlow { ... }
type ClaimDateFlow implements ClaimFlow { ... }
type ClaimLocationFlow implements ClaimFlow { ... }
That’s pretty much it. So we get some generated code where we can use those types as TerminationFlow
instead of Flow
and have the potential mixup between the two.
I’ll start looking into if we can just go ahead and do that then. The only limitation might be if what our backend uses (Netflix DGS) doesn’t support this, or if what we use for iOS also doesn’t support this.
Thanks a lot again 🤗bod
04/04/2023, 1:25 PMStylianos Gakis
04/04/2023, 1:38 PM