[failed test] adding a value after an include

[dwickern]

Given a one-line HOCON config file with an include (and no newline):

include "application"

Adding a value with the ConfigDocument API will produce an invalid config file:

include "application" foo : bar

[raboof]

I assume it does work after adding a trailing newline?

I think we should consider whether HOCON files without a trailing newline should be considered invalid - it seems somewhat common to 'cat' HOCON files together (IIRC that happens when combining reference.conf files, but I could be misremembering), and when files don't have newlines that can lead to problems as well.

[havocp]

I don’t think we can require newline at this point, not backward compatible (and not JSON-superset).

This seems like it will be a fixable bug but I haven’t investigated.

[ennru]

We do not intend to extend the functionality of "Typesafe Config" further. See https://github.com/lightbend/config#maintained-by