[GH-ISSUE #73] Code snippets use " instead of ' #59

Open
opened 2026-05-05 15:00:36 -06:00 by gitea-mirror · 1 comment
Owner

Originally created by @mortomanos on GitHub (Sep 24, 2015).
Original GitHub issue: https://github.com/awatson1978/meteor-api/issues/73

The code snippets use a double quote instead of a single quote which is preferred by eslint.

Originally created by @mortomanos on GitHub (Sep 24, 2015). Original GitHub issue: https://github.com/awatson1978/meteor-api/issues/73 The code snippets use a double quote instead of a single quote which is preferred by eslint.
Author
Owner

@awatson1978 commented on GitHub (Sep 25, 2015):

Yeah, this has come to my attention; and I spent some time trying to reconcile the snippets, linters, and code highlighters. Unfortunately, I don't think it's possible to get it all consistent. The code is accessed in different interpretation contexts (the entire reason that eval() exists in the first place), and setting a universal linting rule is like arguing against a diagonal proof. It's like a mobius strip. If I move the code snippets to use single quotes, it will cause doublequotes complaints elsewhere.

I think my solution moving forward will be to remove the rule that detects singlequote vs doublequote from the default starrynight .eslint file.

<!-- gh-comment-id:143332172 --> @awatson1978 commented on GitHub (Sep 25, 2015): Yeah, this has come to my attention; and I spent some time trying to reconcile the snippets, linters, and code highlighters. Unfortunately, I don't think it's possible to get it all consistent. The code is accessed in different interpretation contexts (the entire reason that `eval()` exists in the first place), and setting a universal linting rule is like arguing against a diagonal proof. It's like a mobius strip. If I move the code snippets to use single quotes, it will cause doublequotes complaints elsewhere. I think my solution moving forward will be to remove the rule that detects singlequote vs doublequote from the default starrynight `.eslint` file.
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/meteor-api#59
No description provided.