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
Using the breaker at line two produces an error because there is a nested chain. It would be great if the function instead looked for the next top level pipe and executed to there (ie line 3).
Alternatively, and perhaps this is up for discussion, it could execute to line two but do so as if that was a complete statement, ie close the parenthesis to get back to the top level and execute, giving the same result as this:
diamonds %>%
mutate(cut = str_to_lower(cut))
The text was updated successfully, but these errors were encountered:
For part 2, I don't think closing expressions is a good idea. Might be hard to do reliably and would give weird errors on edge cases.
Part 1 is something I would like and have thought about a bit. At the moment the search only looks upward. Last time I thought about this, the feature seemed kind of antagonistic against working with nested chains. Nested chains do work, but they often fail if there's a trailing comma, so the trade-off hasn't paid well.
With the following code:
Using the breaker at line two produces an error because there is a nested chain. It would be great if the function instead looked for the next top level pipe and executed to there (ie line 3).
Alternatively, and perhaps this is up for discussion, it could execute to line two but do so as if that was a complete statement, ie close the parenthesis to get back to the top level and execute, giving the same result as this:
The text was updated successfully, but these errors were encountered: