Github user kxepal commented on the issue:
https://github.com/apache/couchdb-config/pull/14
@nickva
After good sleep time I think there is no conflicts here. Yes, features
need to be discovered, but yes, user need to have an option to turn on/off them
easily without doing fancy Erlang tricks.
So config true/false switches is how user may control features
availability. I'm hard to image a case when I would shutdown some feature, but
it looks useful.
So I take my words back, sorry for that.
> Where you thinking of a whole new application or other such thing?
I think new app is a good idea to group there all the features-related
logic which will grow in time. For instance, `config:features` is a bit
misplaced here, but for now there is no better place for it.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
