Describe the bug
When entering a non-breaking space (further nbsp) character sometimes breaks the page it's being located in. This can happen in either section or snippet files, probably others too but those are the tested ones.
Expected behavior
Console will either warn about unexpected character Å/ï in specified line (works as expected) or it will not warn anything and updates the file to store. This causes the "Problem loading page" page to load when accessing the page with faulty characters.
In my case, snippet with nbsp rendered the "Problem loading page" and section with nsbp caused error and canceled deployment. However, my co-worker tested this as well and for them snippet caused errorbut section with nsbp rendered the "Problem loading page".
Notes
My suspicion is that this is some kind of encoding issue with Liquid parsing, but that's not really my area of expertise. Just a hunch!
Environment (please complete the following information):
Describe the bug When entering a non-breaking space (further nbsp) character sometimes breaks the page it's being located in. This can happen in either section or snippet files, probably others too but those are the tested ones.
Shortcuts to produce nbsp, depending on your OS:
You can use this Visual Studio extension to visualize nbsp in your code while reproducing the issue.
To Reproduce Steps to reproduce the behavior:
assign hello = "world"(nbsp)
-- Within filter, e.g.{{ text |(nbsp)strip }}
{{ text | strip(nbsp)}}
Expected behavior Console will either warn about unexpected character Å/ï in specified line (works as expected) or it will not warn anything and updates the file to store. This causes the "Problem loading page" page to load when accessing the page with faulty characters.
In my case, snippet with nbsp rendered the "Problem loading page" and section with nsbp caused error and canceled deployment. However, my co-worker tested this as well and for them snippet caused errorbut section with nsbp rendered the "Problem loading page".
Notes My suspicion is that this is some kind of encoding issue with Liquid parsing, but that's not really my area of expertise. Just a hunch!
Environment (please complete the following information):
ThemeKit 1.3.0 linux/amd
& co-worker:ThemeKit 1.3.0 darwin/amd64