GitHub

  • Commit messages should use the imperative, present tense: “change” not “changed” nor “changes”.
  • refactor: A code change that neither fixes a bug nor adds a feature
  • The repo is used to create a component API for your Angular 1.5 project.
  • perf: A code change that improves performance
  • Run npm run create to create a new component using the Yeoman generator

angular-component-library – Component API for your Angular 1.5 project

@gavynmckenzie: Taking the live styleguide/component library over to Angular 1.x #frontend #javascript #angularjs #styleguides

We recommend upgrading to the latest Safari, Google Chrome, or Firefox.

generators/component feat: Update tests to use chai Dec 8, 2016

gulpfile.babel.js feat: Component variations with mock data Dec 20, 2016

src feat: Component variations with mock data Dec 20, 2016

.babelrc merge Oct 5, 2016

.editorconfig merge Oct 5, 2016

.eslintrc.json feat: styleguide service Oct 6, 2016

.gitignore feat: Code coverage Oct 11, 2016

.scss-lint.yml feat: Add linting and rename this variable to vm Oct 5, 2016

.yo-rc.json feat: Component generator Dec 7, 2016

README.md docs: Generator instructions Dec 8, 2016

karma.conf.js feat: Make karma fail push Dec 9, 2016

package.json feat: Add istanbul back in Dec 9, 2016

This repo is used to create a component API for your Angular 1.5 project.

Fork and clone the repo

to create a new component using the Yeoman generator

Code is linted against: hyphenated_BEM (SCSS), ES6 with Angular plugin

Using Atom you can set up the scss-lint, eslint, and linter-php automatically by installing the following plugins:

Using [SublimeText] you can set up the scss-lint and eslint following these instructions

is run in a pre-commit hook, and if it fails, your code will not be committed.

Commit messages are validated using validate-commit-msg, which follows the Angular commit message guidelines.

Valid types are:

feat: A new feature

fix: A bug fix

docs: Documentation only changes

style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)

refactor: A code change that neither fixes a bug nor adds a feature

perf: A code change that improves performance

test: Adding missing tests

chore: Changes to the build process or auxiliary tools and libraries such as documentation generation

Commit messages should use the imperative, present tense: “change” not “changed” nor “changes”.

Example commit messages:

The components are tested with Karma/Jasmine automatically pre-push.

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.

GitHub