Brandon Kalinowski

I've added a [comment](https://github.com/callstack/linaria/issues/427#issuecomment-497515487) to my RFC that specifically addresses this issue. I've included a lot of detail, but the essence of it is this: Rather than using an arbitrary...

Yes, I have revised by thoughts on the syntax. This is what [I am using](https://www.npmjs.com/package/@brandonkal/linaria) for my ~60 component UI library and it works out quite well. It feels a...

No there is not. You misunderstood what I intended to convey. Take this css: ```css .button { background: pink; } .button__primary { background: green; } .button__disabled { cursor: default; }...

That is a creative solution but I am still not a fan. To provide some reasons: - It necessitates a lot of extra boilerplate and feels less like writing CSS....

The reason I say the object approach requires the css keyword is because no syntax highlighter or linter will accept a plain literal. That last example is just to illustrate...

It seems the toml file it is ignored if I call the file directly. I find that typos often has false positives with SOPS files, for example within the BEGIN...

Even calling `typos --config typos.toml nomad/secrets.sops.yaml` returns the same error. Which is its own bug. So there is no way to configure typos here.

Why is this required if sops is already installed via homebrew?

I was not able to get community.sops working on macOS. So ended up having to use this workaround: ## run//default (playbook=playbooks/setup.yaml) > Run playbook with sops Note that the community.sops...

I am sorry I cannot provide more detail as I have mentioned above I have already found a workaround that always works. Using community.sops plugins broke in weird ways. Maybe...