pveyes / atom-snazzy-clear-syntax

Modern, elegant, clean and consistent Atom syntax theme

Hi there 👋

atom-snazzy-clear-syntax's Issues

Pseudo-selectors deprecation

After updating Atom to v1.13.0, I got this deprecation warning:

“Starting from Atom v1.13.0, the contents of atom-text-editor elements are no longer encapsulated within a shadow DOM boundary. This means you should stop using :host and ::shadow pseudo-selectors, and prepend all your syntax selectors with syntax--. To prevent breakage with existing style sheets, Atom will automatically upgrade the following selectors:”

[Long list of selectors]

Automatic translation of selectors will be removed in a few release cycles to minimize startup time.

Object literal braces should be different from block expression

Use default syntax color for object literal braces

Use better variable naming scheme for color

Currently we use @cyan, @magenta as variable name for selecting color. I think it will be better to use variable that resemble the actual function, e.g @interface @function-call, @html-tag, @object-property etc

At the bottom of colors.css we can write the aliases for them

@interface: @blue
@function-call: @cyan
@html-tag: @red
@object-property: @yellow

Function Flow type alias is magenta

Hi.

When the type-alias is a Function, the color of his name is pink.
Is this intentional?
Personally, I set up a .syntax--flowtype .syntax--function {} rule to change it to either cyan or white.

Anyway, thanks for your great syntax theme.

Dim the color on object destructuring alias

When aliasing using object desctructuring, make sure the unused prop is dimmed

// "a" should be dimmed
// "b" should have variable color
const { a: b } = obj

Group specific style declaration by language

JSX variable interpolation should use the same color as template string var interpolation

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

Snazzy brackets too dark

Just going to say, it looks awesome! But brackets are so dark it makes it a little impractical for work. Could you lift them at least a little bit?