fix #279: Revisit Key behavior

[kirthik]

cc @divega

[kirthik]

Will remove this file in next iteration.

[divega]

👍

[davidfowl]

What will this break?

[divega]

@davidfowl It reverts a break we inadvertently had late in beta7. From #279:

1. We will go back to the previous behavior of Key: configuration.GetSection("A:B").Key == "B"
2. We will add a Path property: configuration.GetSection("A:B").Path == "A:B"
3. We need to make sure that on the API calls on a given node we honor the prefix that applies to it: configuration.GetSection("A").GetSection("B").Path == "A:B"

Last time we made a few changes to other repos to react to configuration changes (which were bigger than this). We will have to look around again to those changes in case we added code that depends on the beta7 behavior.

[kirthik]

cc @divega : updated PR

[divega]

It seemed fine to call this one and assign it to a variable in the beginning. It saves unnecessary method calls.

[kirthik]

@Eilon ya :)

[divega]

We should use Path to get any behavior in derived types.

[kirthik]

cc @divega - updated

[divega]

Nit: parentPath + delimiter is really the prefix 😄

[divega]

[hishamco]

According to 57e808b this must be closed

[kirthik]

merged 57e808b