GitHub user iilyak opened a pull request:

    https://github.com/apache/couchdb-config/pull/2

    2561 make config api consistent

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/iilyak/couchdb-config 
2561-make-config-API-consistent

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/couchdb-config/pull/2.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2
    
----
commit e19b7d5c02b70e14138c9fe1e21f2650100d0a21
Author: ILYA Khlopotov <[email protected]>
Date:   2015-01-29T20:52:29Z

    Remove tests for dropped register functionality
    
    COUCHDB-2561

commit ee24f3ef1a40c1441852dea41061998ac30eb3de
Author: ILYA Khlopotov <[email protected]>
Date:   2015-01-29T20:53:11Z

    Change setup/teardown logic and enable some tests
    
    COUCHDB-2561

commit 82711bfbe91b1dde100d88c9469384ca1dcd564d
Author: ILYA Khlopotov <[email protected]>
Date:   2015-01-29T20:55:27Z

    Callback driven API for config_listener behaviour
    
    This implementaion replaces a mix of message driven and callback driven
    API for config_listener. In particular it replaces gen_event_EXIT
    message with a call to Module:handle_config_stop(Pid, Reason, State).
    This fixes the problem of using config:listen_for_changes in supervisor
    context where there is no way to handle arbitrary messages.
    
    COUCHDB-2561

commit 29d9eaea7255f7f333ec0dec2b3d561236d3be70
Author: ILYA Khlopotov <[email protected]>
Date:   2015-01-29T21:01:21Z

    Enforce type verification for config:set/get
    
    Check the type of given default value to make sure it is supported.
    Raise error(badarg) from set/get on type missmatch.
    Add tests for the feature
    
    COUCHDB-2561

----


---
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.
---

Reply via email to