You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for developing this add-on, it has helped us a lot. Could you help us resolve the error below?
I received the error below from ERB Formatter/Beautify. Later I discovered that if I remove the line break between "<path " and fill-rule="evenodd", keeping a space between the two, the problem is resolved on line 54, but it appears on line 98. I repeat the process and then it appears on line 143.
I tried to identify any illegal character in the file, but I couldn't find it.
Error formatting side_menu_component.html.erb: Formatting failed with exit code 1: /home/igo/.asdf/installs/ruby/3.3.5/lib/ruby/gems/3.3.0/gems/htmlbeautifier-1.4.3/bin/htmlbeautifier:12:in `rescue in beautify': Error parsing standard input: Unmatched sequence on line 54 (RuntimeError)
# after
Error parsing standard input: Unmatched sequence on line 98 (RuntimeError)
# after
Error parsing standard input: Unmatched sequence on line 143 (RuntimeError)
I noticed myself that the parser doesn't like self-closing tags. If you replace all /> with proper closing tags (<path ..></path>, <img ...></img>) in your case, the formatting will finish without run time errors.
However, this is not a problem of this extension, but of the htmlbeautifier gem.
I created a ticket there for this issue: threedaymonk/htmlbeautifier#87
Thank you for developing this add-on, it has helped us a lot. Could you help us resolve the error below?
I received the error below from ERB Formatter/Beautify. Later I discovered that if I remove the line break between "<path " and fill-rule="evenodd", keeping a space between the two, the problem is resolved on line 54, but it appears on line 98. I repeat the process and then it appears on line 143.
I tried to identify any illegal character in the file, but I couldn't find it.
The text was updated successfully, but these errors were encountered: