Frank Schröder

Does it work if you embed them into one large struct?

Does it work if you rename DBConfig to DB in option 1?

Hmm, I get it but this would be a breaking change since this behavior has been in the library since 2014. If you need this then this should be configurable.

I would expect a flag in the `Properties` struct which enables this, e.g. `KeepBackslash`, `RetainBackslash` or something similar which defaults to `false` (i.e. off). Global variable is not ok, unfortunately....

I've thought about this a bit more. The Java properties implementation silently drops **single** backslash characters to avoid tripping over invalid escape sequences. The Go version emulates that behavior. >...

The current `Decode()` method already supports decoding nested maps with the dot notation and array values. Your code duplicates this behavior. The only pieces that are missing are decoding a...

The change in the current form would create the situation that decoding to `map[string]interface{}` is supported whereas decoding to `struct{A map[string]interface{}}` is not. Can you try to work on the...

I can live with the fact that `map[string]interface{}` isn't supported as a struct field type for now. I'll cross that bridge when I get there. I've refactored your code a...

Fields with `properties:"-"` are ignored but that would still be a bug.

When I try this specific example Decode returns an error. Do you check all the errors? Added this to `decode_test.go` ```go func TestDecodeSkipFail(t *testing.T) { type S struct { V...