AdaptiveCards
AdaptiveCards copied to clipboard
[Adaptive Card Templating] Problem with double-quotes in data
This issue was raised some time back- https://github.com/microsoft/AdaptiveCards/issues/4137#issue-634516481. I have the exact same issue with AdaptiveCards.Templating version 1.3.1.
@jwoo-msft - can you take a look?
any updates on this @jwoo-msft ?
Just chiming in here to let you know that we're still running into this issue, today in April 2024, using version 1.3.1
I find it incredible that this is still unresolved and that there does not even appear to be an attempt to fix such a mundane issue. 😓
Just chiming in here to let you know that we're still running into this issue, today in April 2024, using version 1.3.1
I find it incredible that this is still unresolved and that there does not even appear to be an attempt to fix such a mundane issue. 😓
Can you clarify what exactly the issue is? Are you indicating that the text rendered in an AdaptiveCard is not appearing as "\"hi\"'?
For instance, if the template library outputs the following:
{
"type": "AdaptiveCard",
"$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
"version": "1.6",
"body": [
{
"type": "TextBlock",
"text": "\"hi\"",
"wrap": true
}
]
}
you were expecting it would be rendered as "\"hi\""?
Our issue is that we can't seem to be able to render adaptive card templates with string variables surrounded by quotes, e.g. var name = "\"hi\""
However, I was a little hasty in leaving a comment here, as I have been able to run a small test with minimal code and it works fine. I'll get back to you if I'm able to reproduce the issue, but it is possible the problem is due to a mistake in our own code. My apologies.
Our issue is that we can't seem to be able to render adaptive card templates with string variables surrounded by quotes, e.g. var name = "\"hi\""
However, I was a little hasty in leaving a comment here, as I have been able to run a small test with minimal code and it works fine. I'll get back to you if I'm able to reproduce the issue, but it is possible the problem is due to a mistake in our own code. My apologies.