You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was curious if there would be interest in this feature request. If so, I would commit to taking it on (however, I'm not a competent Go developer).
Basically, in our system the UI/Services that consume flags don't necessarily know all the flag id's ahead of time, so sending a list of flag keys (or IDs) to the batch evaluation route requires us to pull all flags first to form the eval request. We've optimized this by caching keys/ids, but it would be great if we could some how request a subset of the flags be automatically included in a batch eval. Perhaps this could be done by filtering a key-value list of metadata on each flag?
Also, we manage the life cycle of our flags based on the flag type, following the categorization denoted by the Thoughtworks piece (https://martinfowler.com/articles/feature-toggles.html). It would be great if there was an arbitrary flag type that could be added to the model (perhaps that should also be metadata?). Right now, we have implemented a hierarchical key structure that allows us to infer the type, but the approach is kind of clunky, and prone to error when users manually manipulate flags in the UI.
BTW - Love the framework; thank you for all the hard work.
The text was updated successfully, but these errors were encountered:
rclayton-the-terrible
changed the title
[Feature Request] Add "flag type" and possibly metadata around flags
[Feature Request] Add "flag type" and possibly metadata to Flag model
Jan 13, 2020
@zhouzhuojie didn't think about just using an array of tags, but I really like the idea. That would avoid adding too much complexity and meet all my needs. I will try to implement it myself and post a PR. Thank you!
I was curious if there would be interest in this feature request. If so, I would commit to taking it on (however, I'm not a competent Go developer).
Basically, in our system the UI/Services that consume flags don't necessarily know all the flag id's ahead of time, so sending a list of flag keys (or IDs) to the batch evaluation route requires us to pull all flags first to form the eval request. We've optimized this by caching keys/ids, but it would be great if we could some how request a subset of the flags be automatically included in a batch eval. Perhaps this could be done by filtering a key-value list of metadata on each flag?
Also, we manage the life cycle of our flags based on the flag type, following the categorization denoted by the Thoughtworks piece (https://martinfowler.com/articles/feature-toggles.html). It would be great if there was an arbitrary flag type that could be added to the model (perhaps that should also be metadata?). Right now, we have implemented a hierarchical key structure that allows us to infer the type, but the approach is kind of clunky, and prone to error when users manually manipulate flags in the UI.
BTW - Love the framework; thank you for all the hard work.
The text was updated successfully, but these errors were encountered: