brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aledsage <...@git.apache.org>
Subject [GitHub] brooklyn-server issue #291: Conveniences to make groups easier to configure ...
Date Mon, 15 Aug 2016 10:30:08 GMT
Github user aledsage commented on the issue:

    https://github.com/apache/brooklyn-server/pull/291
  
    @alasdairhodge we don't have a consistent convention for config key names. We have three
approaches being used:
    * dot-separated - normally used as a hierarchy, but sometimes dots used in the same way
as camelCase (but it shouldn't be)
    * underscores
    * camelCase
    
    Agree would be nice to have consistency! I'm fine with your camelCase.
    
    Merging now.


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message