Closed G-Rath closed 2 months ago
They're intentional, to demarcate a JS property path versus prose words.
ah ok - that doesn't entirely surprise me, but is that a typical thing? I don't think I've ever seen double backquotes used, and meanwhile the sentence starts with a single backquote of a property which is why I decided to open the PR.
Either way no biggie, feel free to close if you want to keep it as is 🙂
ohhh i get it, no, this is indeed just a typo :-) thanks, good catch
sorry I should have included an actual snippet or screenshot 😅
Attention: Patch coverage is 0%
with 1 line
in your changes missing coverage. Please review.
Project coverage is 85.26%. Comparing base (
95849c8
) to head (da626ea
).
Files with missing lines | Patch % | Lines |
---|---|---|
utils/parse.js | 0.00% | 1 Missing :warning: |
:exclamation: There is a different number of reports uploaded between BASE (95849c8) and HEAD (da626ea). Click for more details.
HEAD has 60 uploads less than BASE
| Flag | BASE (95849c8) | HEAD (da626ea) | |------|------|------| ||61|1|
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
I won't admit how many times I'd read this warning while working on #2996 before I realised there were these (cosmetic) double backticks 😅