-
Updated
Nov 12, 2020 - Swift
error
Here are 571 public repositories matching this topic...
-
Updated
Aug 2, 2018 - JavaScript
-
Updated
Oct 28, 2020 - Objective-C
-
Updated
Nov 2, 2020 - JavaScript
-
Updated
Oct 21, 2020 - Objective-C
-
Updated
Nov 14, 2020 - Java
-
Updated
Nov 8, 2020 - JavaScript
-
Updated
Apr 23, 2020 - JavaScript
-
Updated
Aug 11, 2020 - Rust
-
Updated
Jul 29, 2020 - JavaScript
-
Updated
Nov 8, 2020 - JavaScript
-
Updated
Oct 4, 2020 - Go
-
Updated
Aug 24, 2020 - Go
-
Updated
Mar 10, 2020 - Swift
-
Updated
Apr 7, 2020 - Ruby
-
Updated
May 14, 2020 - Python
-
Updated
Feb 13, 2019 - Swift
-
Updated
Nov 12, 2020 - Go
-
Updated
Nov 3, 2020 - Python
-
Updated
Nov 14, 2020 - TypeScript
-
Updated
Nov 4, 2020 - HTML
Improve this page
Add a description, image, and links to the error topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the error topic, visit your repo's landing page and select "manage topics."
Currently the plain text version of the exception and stacktrace are printed in the header and footer of the Ignition response. This makes it easier to spot the exception in a CLI/test runner environment. To avoid XSS we use PHP's
htmlspecialcharacters
function. However, this causes some ugly HTML tags in a plain text output.We should look into replacing some common special characters found