Last 12 weeks · 0 commits
2 of 6 standards met
Relates to:* #20 After searching for way too long to find any information whatsoever on , I stumbled onto this old comment in a issue: https://github.com/github/linguist/issues/3612#issuecomment-300073019. It basically says that wrapping everything after in another set of parens seemed to fix a similar issue for someone else. I'm not sure if this will still fix these issues today, but I did test out the change in locally and it didn't break existing syntax highlighting (as far as I could tell -- I tested it on a component file that includes a lot of -specific features and everything looked good). Because of that, I figured it was worth a shot (since, apparently, there is no way for us to test this with GitHub without actually testing it on* GitHub). ¯\\\_(ツ)_/¯
Repository: sveltejs/svelte-atom. Description: Syntax, diagnostics, and other smarts for Svelte in Atom Stars: 30, Forks: 10. Primary language: JavaScript. Languages: JavaScript (100%). License: MIT. Open PRs: 0, open issues: 4. Last activity: 3y ago. Community health: 50%. Top contributors: rixo, jamesbirtles, kindoflew.
The syntax highlighting is not working on GitHub, both web and mobile, for the `.sveltesvelte{#each}linguistsveltecommunitylinguistlinguistwontfixlinguist svelte const notWorking = 'I am not highlighted'; {#each something as s} Our tags are highlighted correctly {/each} .not-highlighted { color: 'black'; // because it isn't highlighted } svelte const notWorking = 'I am not highlighted'; {#each something as s} Now we aren't working. {/each} .not-highlighted { color: 'black'; // because it isn't highlighted } ``` !Screen Shot 2022-07-26 at 10 19 51 AM !Screen Shot 2022-07-26 at 10 20 10 AM !Image from iOS (6) Related issues: https://github.com/github/linguist/issues/5830 https://github.com/community/community/discussions/13004 https://github.com/community/community/discussions/20556
While doing some research about Atom's LSP ecosystem (for #16), I was able to confirm that we do also have working autocomplete and code formatting in the plugin. As a side note, I'm a bit surprised that the LS doesn't expose code highlight capability... Is that fundamentally different from to getting references? Not that this would make a big difference here, since there's apparently no go-to extension to consume the capability in Atom currently.