fix duplicate ending tag on erb.html files(#3117) #3121
Merged
+0
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The issue manifests in two problematic behaviors: #3117
When modifying an existing ERB tag
<% Time.now %>
by adding=
or#
, the editor incorrectly inserts an additional closing%>
, resulting in malformed ERB syntax.The situation arises very often when you want to comment on a line that already exists in your views.<%#%> Time.now %>
Similarly, when adding a comment symbol
=
, the editor produces invalid nested ERB syntax:<%=%> Time.now %>
This behavior is caused by the autoClosingPairs configuration in the ERB language settings, which automatically adds closing tags in situations where they should not be added.