Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Sanitizing parsers
See original GitHub issueIs your feature request related to a problem? Please describe.
Several people have seen unexpected behaviour due to control codes that have been embedded in the data that they set in a widget - e.g. putting \r characters in the data. This causes all sorts of odd layout problems displaying the widget (as the control codes change location on the screen to something unexpected).
Describe the solution you’d like
Now that we have parsers, how about creating one that simply replaces all control codes with a readable version - e.g. “^M” for \r, etc. Simply add this parser to the widget when you construct it and you never see the issue again!
Added bonus is that this will still maintain the control codes in the data stream should you need to recreate them afterwards.
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
That branch is still under development and so please, by all means, have a look and play, but don’t rely on the API staying the same by the time it is merged into master.
Implemented by #229