Fails to parse uppercase booleans about pureconfig HOT 3 CLOSED

Hi @ruippeixotog,

I am sorry, a miscalculation on my part, I was assuming wrongly it was working before with 0.17.0 , but I checked all versions of pureconfig and uppercase never worked. So I guess this is not really an issue, more a design choice.
I guess we can close this.

from pureconfig.

Hi @fmeeuw! I have just tried reading an uppercase FALSE/TRUE string using v0.17.0 and it didn't work either:

❯ cat build.sbt
libraryDependencies += "com.github.pureconfig" %% "pureconfig" % "0.17.0"

❯ sbt console
scala> ConfigSource.string("b = FALSE").at("b").loadOrThrow[Boolean]
pureconfig.error.ConfigReaderException: Cannot convert configuration to a boolean. Failures are:
  at 'b':
    - (String: 1) Expected type BOOLEAN. Found STRING instead.

  at pureconfig.ConfigSource.loadOrThrow(ConfigSource.scala:81)
  at pureconfig.ConfigSource.loadOrThrow$(ConfigSource.scala:78)
  at pureconfig.ConfigSource$$anon$2.loadOrThrow(ConfigSource.scala:332)
  ... 31 elided

Can you point me out to an old PureConfig version that does this?

from pureconfig.

In this case it's not even PureConfig's design choice, we're following Typesafe Config's rules when it comes to converting config values to booleans, which itself follows the list of supported strings in the HOCON spec. PureConfig readers are often more powerful than Typesafe Config operations, but in this case I think it makes sense for us to stick with the HOCON spec. Nothing prevents you from writing your ConfigReader for this, of course 🙂

from pureconfig.