Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
How can I have multiple classes of actors? #11
I tried to keep the idea of actor to be generic. What you use as your actor can be whatever makes sense for the feature. It could be tricky to use actors for both as they could have conflicting ids. That said, when I switch ids to be strings you could do your own concatentation trickery to make it work.
I'm certainly open to suggestions. I'm not quite using flipper in production yet, so there could be a few small things that are odd and need tweaked.
This comment has been minimized.
This comment has been minimized.Show comment Hide comment
With rollout I just created two instances of the rollout object, one for each type, but that doesn't really make as much sense here, because the goal of flipper seems to be wider.
Thinking about it more, I guess there isn't anything preventing passing different kinds of objects as the actor to different named features, as long as you keep track of it in your app code, it shouldn't make a difference...