Unable to put a literal * into visualizer
See original GitHub issueDepending on the number of * it behaves differently. Escaping it doesn’t seem to help either
{
"$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
"type": "AdaptiveCard",
"version": "0.5",
"body": [
{
"type": "TextBlock",
"text": "**********",
"wrap": true,
"maxLines": 2
}
]
}
Issue Analytics
- State:
- Created 6 years ago
- Comments:14 (14 by maintainers)
Top Results From Across the Web
invalid literal for int() with base 10: '' using ANN Visualizer - ...
Make sure that lstm_model is a Keras Sequential model view (ann_visualizer on pypi). It seems that this same problem was issued on github...
Read more >Z Game Editor | How to Make Beat Visualizers in FL Studio
Your browser can't play this video. Learn more.
Read more >How to fix this ValueError invalid literal for int with base 10 ...
ValueError: invalid literal for int() with base 10: ''.` It is reading the first line but can't convert it to an integer.
Read more >Getting error on array literal notation [ ] Can't figure it out...
Cannot figure out why this code won't work. The only error I'm getting is on the var family = new Array(); Any help...
Read more >Understanding Aphantasia
Firstly, because my inability to visualize had an actual name! ... In fact, aphantasia encapsulates the act of visualization, or “picturing” ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Still relevant today. My preferred solution is to allow opting out of Markdown. Like Andrew I would rather make it an opt-in thing, but we have shipped with Markdown processing always applied. We can’t remove that.
You mean RichTextBlocks without markdown support, and yes that would solve it, but that’s a less-ideal way of solving it. We simply need to have a property on TextBlock that lets you disable markdown.