This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
import { LitElement, html } from 'lit'; | |
/* | |
This mimics the behavior of <slot>s in a light DOM LitElement. It supports both | |
named slots (`<slot name="foo">`) and anonymous slots (`<slot>`). This has not | |
been heavily tested yet, but seems to work for most simple use cases using | |
Lit 3.1.4. | |
There are a few minor differences between Shadow DOM and this, particularly if: | |
- you attempt to add content to a named slot but that slot isn't defined in the |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
twitter.com##.module.trends | |
twitter.com##.wtf-module | |
twitter.com##[data-component-context="suggest_activity_tweet"] | |
twitter.com##.nav>.moments | |
twitter.com##.LiveVideoHomePageModuleContainer |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
atom-text-editor.editor .linter-highlight.linter-error .region, | |
.linter-highlight.linter-error .region { | |
background-image: | |
linear-gradient(45deg, transparent 65%, @red-5 80%, transparent 90%), | |
linear-gradient(135deg, transparent 5%, @red-5 15%, transparent 25%), | |
linear-gradient(135deg, transparent 45%, @red-5 55%, transparent 65%), | |
linear-gradient(45deg, transparent 25%, @red-5 35%, transparent 50%) !important; | |
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
/* | |
I agree w/ the philosophy of Prettier, that as few options as possible should be | |
provided. However issues that are hot-button (e.g. tabs vs spaces) and would actively | |
prevent a large number of devs from using the tool should be configurable. The the ones | |
that jump immediately to mind for me are | |
1) tabs vs spaces (& number of spaces) | |
2) line length | |
3) reordering properties (more on that below) | |
These are my preferences, but I’m putting everything on the table in the spirit of |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
:root { | |
--main-color: red; | |
--secondary-color: color(var(--main-color) hue(20%)); | |
} | |
.module-one { | |
color: var(--main-color); | |
} | |
.module-two { |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
[alias] | |
log-pretty = log --graph --pretty=format:'%Cred%h%Creset -%C(yellow)%d%Creset %s %Cgreen(%cr) %C(black)%cn%Creset' --abbrev-commit --date=relative |