Amit K Gupta
Amit K Gupta
With tagValueProcessor you can control how and which tag value should be parsed. - If tagValueProcessor returns undefined or null then original value would be set without parsing. - If...
Yes, you're right. People can skip parsing by just returning `undefined`. In my understanding, you want to call "tagValueProcessor" for empty values and set the value as per your need....
You can refer the branch that I created to understand the impact better
@Marius8881 Can you please give some example? I'm working on fxp v4. I can probably consider new requirements in that.
Do you expect `overlays = ' '` in case of ` ` ?
Try `trimValues: false`. But it may add `"#text": "\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n",` to the output.
closing as no update. reopen it if issue still exists
@fpedroza Currently no. But you can create another issue for a feature request. If there are more users who are looking for the same or similar behavior then we can...
Let's assume 2 situation `` and `text`. Should we call `tagValueProcessor` for ``?
I've created a branch "emptyNode_v2" for this change. But not publishing them due to a few pending decisions like when not to call tagValueProcessor.