dc-
.dc-
and must use the hyphen-case (with hyphens as separators)._dc-*
Each atom/molecules/module is prepared to be independently loaded, by requiring its own dependencies. So you will notice at the top of each file a commented import directive, something like this:
// @import "../core/core";
@mixin dc-checkbox($sibling-label-selector : ".dc-label") {
// ...
}
We hope that sass 4 brings us a new cool import directive that works as the less one (import once by default). We are not the only one requesting that feature
The git workflow that we use to contribute is mostly based and well explained in this article: a-successful-git-branching-model
If a github issue is related to a branch we suggest to append the number at the end of the branch name.
example: topic/dropdown-refactor-98
We have very precise rules over how our git commit messages can be formatted. This leads to more readable messages that are easy to follow when looking through the project history. It is important to note that we use the git commit messages to generate the Dress Code Changelog document.
A detailed explanation of guidelines and conventions can be found in this document.
Each commit message consists of a header, a body and a footer. The header has a special format that includes a type, a scope and a subject:
<type>(<scope>): <subject>
<BLANK LINE>
<body>
<BLANK LINE>
<footer>
Any line of the commit message cannot be longer 100 characters!
This allows the message to be easier to read on github as well as in various git tools.
Must be one of the following:
The scope could be anything specifying the place of the commit change.
The subject contains succinct description of the change:
Just as in the subject, use the imperative, present tense: "change" not "changed" nor "changes" The body should include the motivation for the change and contrast this with previous behavior.
The footer should contain any information about Breaking Changes and is also the place to reference GitHub issues that this commit Closes.
Breaking Changes are intended to highlight (in the ChangeLog) changes that will require community users to modify their code with this commit.
refactor(button): prefix btn class with dc-
BREAKING CHANGE: btn class now is prefixed with dc namespace.
Change your code from this:
```html
<button class="btn">submit</button>
```
To this:
```html
<button class="dc-btn">submit</button>
```
<semver>
placeholder stay for a new semantic version (e.g. 0.4.1).
For more info, please take a look here.git checkout -b release/<semver>
npm run build
bower.json
and package.json
npm run changelog
CHANGELOG.md
).
When done, commit the changes and push the release branch.git add --all;
git commit -m "chore(release): <semver>";
git push -u;
When the CI job pass with SUCCESS, merge or rebase the release branch on top of the master branch.
git checkout master;
git pull;
git rebase release/<semver>; # or open a pull request to master
git tag -a <semver> -m "<semver>";
git push origin master;
git push origin <semver>; # push the tag
npm run deploy:demo;
npm publish
git checkout develop;
git rebase master; # or git merge
git push origin develop;