akutz / gofig

85%

master: 75%

LAST BUILD ON BRANCH feature/scope-with-prefix

branch: feature/scope-with-prefix

CHANGE BRANCH

x

Reset

• feature/scope-with-prefix
• bugfix/copy-scope
• bugfix/explicit-names
• bugfix/pflag-compile
• bugfix/scope-parent
• bugfix/test-pflag-builds
• feature/gotil
• feature/interfaces-opt-pflag
• feature/multi-regs
• feature/override-registrations
• feature/rm-pflag-tag
• feature/scope
• feature/scoped-prefixes
• feature/secure-json
• feature/viper-nofork-yaml
• feature/yaml-validation
• master
• v0.1.0
• v0.1.1
• v0.1.2
• v0.1.3
• v0.1.4
• v0.1.5
• v0.1.6
• v0.1.7
• v0.1.8
• v0.1.9

Build # 41

Build Type

push

travis-ci

Committed by akutz

Commit Message

Scope with Prefix

This patch introduces a new function, `ScopeWithPrefix`.

ScopeWithPrefix returns a scoped view of the configuration like the
Scope function, but this variant allows the specification of a prefix.
The prefix enables the creation of a scoped configuration that does
not have the fully-qualified paths to the desired configuration keys.
For example, imagine the following YAML:

    gofig:
      logging:
        enabled: true
      modules:
        admin:
          gofig:
            logging:
              enabled: true

To enable or disable logging the key is `gofig.logging.enabled`, but
the modules may require their own distinct values controlling logging
when using a scoped configuration via `Scope("gofig.modules.admin")`.
However, unless the complete key path of `gofig.logging.enabled` is
replicated under each named module, this isn't possible using the
standard key `gofig.logging.enabled`.

Using `ScopeWithPrefix("gofig.modules.admin", "gofig")` it is now
possible to enable the following YAML configuration so that the
scoped configuration can still use the `gofig.logging.enabled` key to
access the property value.

    gofig:
      logging:
        enabled: true
      modules:
        admin:
          logging:
            enabled: true

The prefix value is simply removed from key requests such that an
attempt to access the key `gofig.logging.enabled` actually results
in the access attempt using the key `logging.enabled`.

Run Details

431 of 506 relevant lines covered (85.18%)

73.63 hits per line