Example of bad vs good ratpack configuration usage

ratpack-config-usage.groovy

// a config class with a default value
class LogConfig {
    boolean logRequestBody = false
}

// in ratpack, the LogConfig is bound with a prefix of `/logging`
Ratpack.groovy {
  bindings {
    bindInstance(serverConfig.get('/logging', LogConfig))
  }
}

// BAD: code usage of the config just references the `LogConfig` without the prefix
// the end result is that it'll ignore any overrides that use the prefix `/logging`, and only ever use the
// default config value in the LogConfig class.
if (context.serverConfig.get(LogConfig).logRequestBody) {
  // do something
}

// i.e. this won't pick up the change
./gradlew -Dlogging.logRequestBody=true run

// GOOD: when accessing the config, make sure the config prefix matches how it's bound in Ratpack.groovy:
if (context.serverConfig.get('/logging', LogConfig).logRequestBody) {
  // do something
}