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
The one thing I am not sure about is what to do about unexecuted code blocks like these:
```{{r}}1+1```
Should they be linted? Currently, out of the box, we don't. Should that be changed?
Note that, since these are verbatim blocks, even the directive to not lint will show up, which is not desirable:
```{{r}}1+1 # nolint```
I personally think they shouldn't be linted since the intent behind these blocks seems to be to show the code as it is, but if we style/lint them, then we are undoing that intent. For example, these blocks can be used to show what code with lints looks like. That said, I am open to hear what other people think.
Activity
Updates docs and adds tests for Quarto files
IndrajeetPatil commentedon Sep 24, 2022
The one thing I am not sure about is what to do about unexecuted code blocks like these:
Should they be linted? Currently, out of the box, we don't. Should that be changed?
Note that, since these are verbatim blocks, even the directive to not lint will show up, which is not desirable:
I personally think they shouldn't be linted since the intent behind these blocks seems to be to show the code as it is, but if we style/lint them, then we are undoing that intent. For example, these blocks can be used to show what code with lints looks like. That said, I am open to hear what other people think.
cc @mine-cetinkaya-rundel
MichaelChirico commentedon Sep 24, 2022
essentially the same issue as #773
IndrajeetPatil commentedon Sep 25, 2022
@MichaelChirico Good to know.
Should we keep #1487 pending until this is resolved, or come back to dealing with these blocks in a later PR?
Update docs and adds tests for Quarto files (#1487)