A lista de issues deste repositório é exclusivamente para lista de erros e solicitações de recursos. As issues não conformes serão fechadas imediatamente.

Para perguntas gerais, junte-se à comunidade.

Tente procurar por seu problema, ele pode ter sido respondido.

Veja se o erro é reprodutível com a versão mais recente.

Se reprodutível, forneça um simples codepen ou um repositório que pode ser clonado para produzir o comportamento esperado.

Por favor, use o criador de issues para criar uma nova issue.

Vuetify contains a local dev environment that you can bootup to test new features, functionality, and components. Before you can get started however, there are a few things you will need to install that will assist you in managing the many aspects of vuetify.

The Vuetify team uses Commitizen for all repository commits. This allows for easy to read and organized commits with minimal change to normal commit functions. To get started install Commitizen globally using npm:

Congrats! Commitizen is installed! When you do commits, add your files like normal and replace git commit -m "your message" with git cz and follow the prompts.

See "Commit Guidelines w/Commitizen" below for commit guidelines

If you choose, you can use PM2 to run and manage multiple portions of the Vuetify mono-repo at the same time (Playground, Docs, Etc...) Included in the root directory are a few PM2 config files which will boot up and manage all that Vuetify has to offer. To get started you need to start PM2:

Setting up your dev environment is easy! To start fork Vuetify into your own repo.

Now you are ready to boot up your dev environment!

There are a few ways to startup the dev environments in Vuetify mono-repo:

To import pre-configured PM2 instance use the following

Here are some commands to use with PM2 to start/stop/restart instances

Commitizen provides a fluid interface for handling semantic versioning. This provides a great boilerplate making it easier to write patch notes.

All commits should use commitizen with the conventional-changelog as noted above. Commits should follow the format <type>: <subject> or <type>(scope): <subject>

• feat: Commits that result in a new features or functionalities. Backwards compatible features will release with the next MINOR whereas breaking changes will be in the next MAJOR. The body of a commit with breaking changes must begin with BREAKING CHANGE, followed by a description of how the API has changed.

• fix: Commits that provide fixes for bugs within vuetify's codebase.

• docs: Commits that provide updates to the docs.

• style: Commits that do not affect how the code runs, these are simply changes to formatting.

• refactor: Commits that neither fixes a bug nor adds a feature.

• perf: Commits that improve performance.

• test: Commits that add missing or correct existing tests.

• chore: Other commits that dont modify src or test files.

• revert: Commits that revert previous commits.

Before doing any commits, you will want to pull down the latest and greatest from dev. From here, merge, and resolve any conflicts between your branch and dev. Its a good rule of thumb to pull frequently as development is constantly happening.

In git, add all relevent files.

Commit with commitizen using the command git cz. From here you will follow through a series of props. Make sure to select the appropiate type (see Commit Guidelines w/Commitizen above)

Lastly, git push and open a pull request.