TYPO3.Fluid

Problem:
All TypoScript settings are made available under $this->settings inside the Controller, and as well as {settings} inside the template. To be more close to FLOW3 and because the "." (dot) is the separator in Object Accessors, we needed to strip the trailing "." in TypoScript configuration away.
Thus, when one writes the TypoScript:
10 = TEXT
10.value = Hello
then, in classical TYPO3 v4, this gets converted to the following array:
array(
'10' => 'TEXT'
'10.' => array(
'value' => 'Hallo'
)
)
However, Extbase converts it to the following (because of the above reasons)
array(
'10' => array(
'value' => 'Hallo',
'_typoscriptNodeValue' => 'TEXT'
)
So, what happens is that the value of the actual TypoScript node is pushed down into its substructure.
This works really well, and solves most cases, but imagine the following case:
Inside your ViewHelper, you expect a configuration for a cObject which you'll render using the classical tslib_cObj. Thus, you'll need the "classical" TYPO3 v4 syntax (with trailing dot), but Extbase only provides you the 2nd syntax with _typoscriptNodeValue.

Job description:
Write a helper method you can call inside your custom ViewHelper which converts the "Extbase" TypoScript to "classical" TypoScript by re-introducing the "." where needed and remove the _typoscriptNodeValue.
Test it with unit tests.
I propose that the class should be called Tx_Extbase_Utility_TypoScript.