Github user nickva commented on the issue:
https://github.com/apache/couchdb-chttpd/pull/144
@kxepal
> So semantically, object is better here since we guarantee only one
feature presence and we can raise conflicts exceptions with easy.
Can just as easily write code which overwrites a feature object key just as
can do lists:usort on the features list before returning. Or if we want server
to crash can easily check for `lists:usort(Features) = lists:sort(Features)`
before returning the request.
I still don't see having to manage an object as being a lot better than a
simple list of labels
---
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.
---
