fix object_usage_linter with new xml2lang to avoid parsing comments #1935
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…n multi-line expr
Codecov Report
@@ Coverage Diff @@
## main #1935 +/- ##
=======================================
Coverage 98.85% 98.85%
=======================================
Files 112 112
Lines 4874 4876 +2
=======================================
+ Hits 4818 4820 +2
Misses 56 56
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
|
Yeah, it could. A PR is welcome. |
IndrajeetPatil
approved these changes
Mar 26, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #1919
@gaborcsardi, this helper (for going from xml back to parseable R code) might be something {xmlparsedata} could export, WDYT?
For now I'm leaving it as an internal helper here.