John Nunemaker

I'm excited to look through this but I'm on vacation this week. Just wanted you to know that's why I'll probably be slow to respond fully.

A concrete example of how this would be cool. For flipper cloud, say we have an api feature. Its always enabled. If we made it possible to disable for individual...

Yeah that could work. We’d still need to adjust api, ui, adapters and Feature but that verbiage could help make it all more clear. We’d also still need a way...

I totally love this idea. I was thinking that likely the easiest way would be some sort of hydrator for actors. Given a dehydrated actor id (or ids) it invokes...

Another alternative would be to store this along with the actor id but becomes a cache invalidation issue pretty quick.

You definitely can. The problem is that people change their email addresses so you’d need to be sure to update flipper if so.

Worth mentioning I laid out a plan for this if someone has the time to make a PR. https://github.com/jnunemaker/flipper/issues/657#issuecomment-1215365903

@AlexWheeler I don't think I'm picturing quite that, for the reasons you mention. Standardizing is important or how will all the tools built on flipper know what to do. What...

@st33b I'm really torn on v2. At first I was really excited, but I'm starting to think new adapter methods instead of even more dumbed down adapters isn't that bad...

I think it totally makes sense to drop "features" and just have "/" be the main route if we can make it work. I can't remember why I did it...