You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 7, 2020. It is now read-only.
This is a pretty minor point, but there are some stylistic differences between js-assessment and these answers. The one that stood out to me is that in this app there's a space after colons (ref), whereas this doesn't seem to be the style in js-assessment.
Maybe we can do a quick comparison of the code styles and whip up a PR to make them more consistent.
The text was updated successfully, but these errors were encountered:
I 💘 jscs, but at the moment this repo is pretty lightweight, being just the javascript files themselves with nothin' else. It's not a huge decision, but it is a notable change if we were to add jscs. Presumably it could be as simple as adding a package.json manifest and an inline script to run the command, along with the .jscsrc file.
Another option would just be to loosely follow the convention in a manual way. It'd be less precise, but maybe good enough for the purposes of this little library?
i think the reason i like jscs would be that it documents itself, and then people who contribute know what needs to happen so we don't have to nitpick their PRs. saves us on maintenance, gives contributors confidence.
This is a pretty minor point, but there are some stylistic differences between js-assessment and these answers. The one that stood out to me is that in this app there's a space after colons (ref), whereas this doesn't seem to be the style in js-assessment.
Maybe we can do a quick comparison of the code styles and whip up a PR to make them more consistent.
The text was updated successfully, but these errors were encountered: