Quasar Framework Contributing Guide     

I’m really excited if you are interested in contributing to Quasar Framework. There are lots of features waiting for someone to write them. Check Github or contact Razvan Stoenescu through email.

Before submitting your contribution though, please make sure to take a moment and read through the following guidelines.

You can also help with the documentation if you catch a mistake or want to add a few lines to a page or write new pages. Use the link at the end of each page of this website (specifically the Suggest an edit on Github).

Finally, if you want, you can leave a buck for coffee from time to time. Quasar needs some financial backing to evolve. Read more here.

Github Repositories

Issue Reporting Guidelines

Please use the appropriate Github repo to report issues. See “Github Repositories” above. For example, a bug related to CLI should be reported to the CLI repo, one related to build issues to Quasar Framework Templates repo and so on.

Pull Request Guidelines

Code Style

Development Setup

You will need Node.js along NPM. Read package.json and take notice of the scripts you can use.

Commit Message Format

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>

The header is mandatory and the scope of the header is optional.

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.

Revert

If the commit reverts a previous commit, it should begin with revert:, followed by the header of the reverted commit. In the body it should say: This reverts commit <hash>., where the hash is the SHA of the commit being reverted.

Type

Must be one of the following:

Scope

The scope could be anything specifying place of the commit change. For example use modules as scope name: xhr, router, view etc…

Subject

The subject contains succinct description of the change:

Body

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 should start with the word BREAKING CHANGE: with a space or two newlines. The rest of the commit message is then used for this.