Update repository description about ecmascript-sublime HOT 3 CLOSED

@bathos

It seems wise to keep the final qualifier there

Agreed - "absurdly specific scopes" is succinct and catchy!

we should probably drop "Sublime" since it’s redundant

Good point, although it probably helps discoverability when searching the web. Then again, "Sublime" is also in the name of the package.

Something else to consider is that PackageControl (or ST3?) is cutting text from the description line if it is too wide for the command palette modal.

This probably varies slightly platform to platform, but if it's too long then words are removed starting from the middle. Although, the descriptions are not searchable from the command palette anyway.

Based on some back-of-the-pixel font metrics I just did, if you truncate what you suggest by just removing the word "definition", then it fits the modal width:

ECMAScript/JavaScript syntax (ES2015-ES2018, JSX, template highlighting, etc) with absurdly specific scopes

from ecmascript-sublime.

LGTM — updated it. Unsure if Package Control will pick that up automatically or if it only “takes” when it detects a new release, but I suppose we’ll know in a few hours.

from ecmascript-sublime.

It gets pulled in by Package Control as the package description, right?

I thought about adding more keywords last time I updated the Package Control entry but was reluctant to be comprehensive for fear of it being spammy. Expanding the repo desc is a good idea, probably the more kosher way to make it discoverable / clarify its purpose.

Right now it’s "Sublime-syntax definition for ES6+ with absurdly specific scopes". It seems wise to keep the final qualifier there since it’s one of the main distinguishing features of this package — there are a lot of choices out there so emphasizing the focuses might help people determine which one is most likely to be what they’re looking for (detail vs compatibility, accuracy vs speed, etc).

Given the desc gets displayed in that context, we should probably drop "Sublime" since it’s redundant (unless somebody knows that "sublime syntax" is distinct from tmLanguage, but I don’t think that’s generally useful info to somebody searching package control).

Something like this might be an improvement:

ECMAScript/JavaScript syntax definition (ES2015-ES2018, JSX, template highlighting, etc) with absurdly specific scopes

Too much? Not enough?

from ecmascript-sublime.