The scalatest dependency should be in "test" scope?

e.g.
libraryDependencies += "org.scalatest" %% "scalatest" % "1.6.1" % "test"

Hey there,
Configrity seems to be throwing exceptions when parsing Files that contain whitespaces in the path. Is this a bug?

example of configuration:

managed {
  directories = [C:\Users\arg\Documents\RCT3,C:\Users\arg\Documents\StarCraft II\Accounts\662168\2-S2-1-821040\Replays\Multiplayer]
}

I should mention that the configuration file is generated by the library itself.

we have here a list of files, this error is thrown:

org.streum.configrity.io.StandardFormat$ParserException: [2.79] failure: `]' expected but `I' found

  directories = [C:\Users\arg\Documents\RCT3,C:\Users\arg\Documents\StarCraft II\Accounts\662168\2-S2-1-821040\Replays\Multiplayer]

Please add support for YAML as configuration Format.

Valid YAML file:

mixer:

hardware:
    device: "/dev/ttyUSB0"

Code to load it:

Configuration.load("config.yaml", YAMLFormat)

Traceback:

Exception in thread "main" java.lang.NullPointerException
    at org.streum.configrity.yaml.YAMLFormat$.org$streum$configrity$yaml$YAMLFormat$$readValue(YAMLFormat.scala:70)
    at org.streum.configrity.yaml.YAMLFormat$$anonfun$readMap$1.apply(YAMLFormat.scala:62)
    at org.streum.configrity.yaml.YAMLFormat$$anonfun$readMap$1.apply(YAMLFormat.scala:61)
    at scala.collection.TraversableOnce$$anonfun$foldLeft$1.apply(TraversableOnce.scala:144)
    at scala.collection.TraversableOnce$$anonfun$foldLeft$1.apply(TraversableOnce.scala:144)
    at scala.collection.immutable.Map$Map3.foreach(Map.scala:154)
    at scala.collection.TraversableOnce$class.foldLeft(TraversableOnce.scala:144)
    at scala.collection.AbstractTraversable.foldLeft(Traversable.scala:105)
    at org.streum.configrity.yaml.YAMLFormat$.readMap(YAMLFormat.scala:61)
    at org.streum.configrity.yaml.YAMLFormat$.yaml2map(YAMLFormat.scala:52)
    at org.streum.configrity.yaml.YAMLFormat$.fromText(YAMLFormat.scala:34)
    at org.streum.configrity.Configuration$.load(Configuration.scala:231)
    at org.streum.configrity.Configuration$.load(Configuration.scala:246)
    at my.code.Blub$.load(Config.scala:132)

Hey there, it looks like I found another bug. It seems like configrity saves empty string like so:

 some.key = 

but isn't able to parse such format. It throws following error:

! org.streum.configrity.io.StandardFormat$ParserException: [7.12] failure: `}' expected but `=' found
! 
!   password = 
! 
!            ^
!   at org.streum.configrity.io.StandardFormat$Parser$class.parse(StandardFormat.scala:78)

Adding manually " " into config file resolves the issue.

In a system where a big Configuratin is read from various sources and then different sections are detached and provided to components for internal configuration.

This components need to report configuration errors but, as is, can't report correctly the full path since the detached config doesn't carry the "path" from where it was detached.

So it would be nice if when you detach a configuration it would keep a string with de parameter passed to detach itself and expose it through a simple read-only property.

val configuration = Configuration(....)
val detached = configuration.detach("some.config.section")
// then:
assert detached.contextName == "some.config.section"

I gave not much thought to the contextName name.

If this makes general sense, I can offer a patch.

I suddenly found myself needing strings with double quotes, and there seems to be no way of adding them. A simple solution would be to allow strings formed by single quotes, though that would still leave out things that need both single and double quotes.

There doesn't seem to be a Configrity release for Scala 2.10.0.

Scala 2.10 has not been announced publicly, but it has already been released to
Typesafe repositories so that library authors can make a version of their library
available for 2.10 prior to its public announcement. This makes the release process
go smoother (and people will be happier to upgrade).

It woud be great to have a release of Configrity for Scala 2.10 available as well.

Hi there,

I wonder if it is possible to add usage of environmental variables in a config file? The thing is I rely on the env variable that has a changeable value.

I'd like to be able to use the style similar to the following one:

my.env=${MY_ENV}

As I understand TypeSafe config has this feature.

Best regards,

Dmytro Zhydchenko.

To configure a value in the code which represents a List we have to write something like this:

val config = Configuration(
...
"some.key.1" -> "[10]"
"some.key.2" -> "["some string"]"
...
)

which looks ugly. What I would like to do is this:

val config = Configuration(
...
"some.key.1" -> List(10)
"some.key.2" -> "some string" :: Nil
...
)

Thanks!

Could we provide a way to configur LogBack using Configrity, so that all the config related to an application could be at one place.

Let me demonstrate.

import org.streum.configrity._
val config = Configuration()
val config2 = config.set("foo",""""bar bar"""")
config2.save("foo.conf")
val config3 = Configuration.load("foo.conf")

val res1 = config2[String]("foo")
val res2 = config3[String]("foo")

Results in res1 equaling "bar bar". However res2 equals bar bar, that is a string that doesn't contain double quotes. What is happening is that while loading Configrity strips off the double quotes.

I think that to be consistent Configrity should keep the double quotes.

Any plans for support?

Configrity could support Domain's which can be picked up from the environment.

This could be used to pick up different config in different environments like Testing, Production, Development.

When building an application with complex configuration read from many sources it is desirable being able to report precisely on the source location of any given setting when appropriate.

For example when reporting configuration errors it is highly desirable being able to report precisely the source of the conflicting setting to facilitate fixing the situation.

Another example is when reporting some collection of configuration settings for user checking.

I believe for input formats, the "precise source" of the setting would be a pair of location of resource and line number from where the setting effective value has been read.

During the test of an application, we had some comments in the configuration loaded via loadresource, like

# key =

The configuration is always complaining about the wrong assigment:

org.streum.configrity.io.StandardFormat$ParserException: [7.3] failure: `=' expected but `k' found