Skip to content

Latest commit

 

History

History
226 lines (157 loc) · 7.96 KB

CONTRIBUTING.md

File metadata and controls

226 lines (157 loc) · 7.96 KB
Raw

Thanks for showing interest to contribute to Chakra UI 💖, you rock!

When it comes to open source, there are different ways you can contribute, all of which are valuable. Here's a few guidelines that should help you as you prepare your contribution.

Setup the Project

The following steps will get you up and running to contribute to Chakra UI:

  1. Fork the repo (click the Fork button at the top right of this page)

  2. Clone your fork locally

git clone https://github.com/<your_github_username>/chakra-ui-vue-next.git
cd chakra-ui
  1. Build components
yarn build
  1. Setup all the dependencies and packages by running yarn bootstrap. This command will install dependencies and bootstrap the repo using lerna
yarn bootstrap

If you run into any issues during this step, kindly reach out to the Chakra UI Vue team here:https://discord.gg/cMpMfvxa

Development

To improve our development process, we've set up tooling and systems. Chakra UI uses a monorepo structure and we treat each component as an independent package that can be consumed in isolation.

Tooling

  • Lerna to manage installation of dependencies and running various scripts. We also have yarn workspaces enabled by default.
  • Testing Library for testing components and hooks
  • Vite SSR for a blazing fast documentation website. versioning and changelogs
  • Changeset for changes documentation, changelog generation, and release management.

Commands

yarn install: bootstraps the entire project, symlinks all dependencies for cross-component development and builds all components.

yarn bootstrap: bootstraps the entire project and symlinks all dependencies for cross-component development.

yarn dev: starts components playground server and loads stories in SFCs in the packages/**/examples/*.vue file.

yarn docs:dev: run the documentation site locally.

yarn docs:build: run build for all component packages.

yarn test: run test for all component packages.

yarn release: publish changed packages.

yarn pkg [package] <cmd>: Run a command on the specific package you're working on. You can run build, test, lint commands.

Package Aliasing and Yarn Workspace

Since we're using lerna monorepo + yarn workspaces by default, this enables us to run commands within component packages directly from the root.

Each component is named this way: @chakra-ui/[component]. Let's say we want to build the button component. Here's how to do it:

Take note that in order to prevent template tags name clashing with HTML elements or other Vue library components, we prefix all component names with a c- in kebab-case or a capital C in PascalCase.

yarn workspace @chakra-ui/c-button build

# or

lerna run build --scope @chakra-ui/c-button

Shortcut:

# to build
yarn pkg @chakra-ui/c-tabs build

# to test
yarn pkg @chakra-ui/c-tabs test
yarn pkg @chakra-ui/c-tabs test --watch

This alias is particularly useful when you're working on a specific component and want to avoid running the command for all components.

Documentation

The documentation site is built with Vite.js on SSR. If you'd like to contribute to the docs, simply run yarn build, and yarn docs:dev

Components Development Playground

Build components in isolation with Storybook using yarn dev

Think you found a bug?

Please conform to the issue template and provide a clear path to reproduction with a code example. The best way to show a bug is by sending a CodeSandbox link.

You may wish to use our starters to help you get going:

TODO: Add Typescript starter for @chakra-ui/vue v1 TODO: Add Javascript starter for @chakra-ui/vue v1

Proposing new or changed API?

Please provide thoughtful comments and some sample API code. Proposals that don't line up with our roadmap or don't have a thoughtful explanation will be closed.

Making a Pull Request?

Pull requests need only the 👍 of two or more collaborators to be merged; when the PR author is a collaborator, that counts as one.

Commit Convention

Before you create a Pull Request, please check whether your commits comply with the commit conventions used in this repository.

When you create a commit we kindly ask you to follow the convention category(scope or module): message in your commit message while using one of the following categories:

  • feat / feature: all changes that introduce completely new code or new features
  • fix: changes that fix a bug (ideally you will additionally reference an issue if present)
  • refactor: any code related change that is not a fix nor a feature
  • docs: changing existing or creating new documentation (i.e. README, docs for usage of a lib or cli usage)
  • build: all changes regarding the build of the software, changes to dependencies or the addition of new dependencies
  • test: all changes regarding tests (adding new tests or changing existing ones)
  • ci: all changes regarding the configuration of continuous integration (i.e. github actions, ci system)
  • chore: all changes to the repository that do not fit into any of the above categories

If you are interested in the detailed specification you can visit https://www.conventionalcommits.org/ or check out the Angular Commit Message Guidelines.

Steps to PR

  1. Fork of the chakra-ui-vue repository and clone your fork

  2. Create a new branch out of the main branch. We follow the convention [type/scope]. For example fix/accordion-hook or docs/menu-typo. type can be either docs, fix, feat, build, or any other conventional commit type. scope is just a short id that describes the scope of work.

  3. Make and commit your changes following the commit convention. As you develop, you can run yarn pkg <module> build and yarn pkg <module> test to make sure everything works as expected. Please note that you might have to run yarn boot first in order to build all dependencies.

  4. Run yarn changeset to create a detailed description of your changes. This will be used to generate a changelog when we publish an update. Learn more about Changeset. Please note that you might have to run git fetch origin main:master (where origin will be your fork on GitHub) before yarn changeset works.

If you made minor changes like CI config, prettier, etc, you can run yarn changeset add --empty to generate an empty changeset file to document your changes.

Tests

All commits that fix bugs or add features need a test.

Dear Chakra UI Vue team: Please do not merge code without tests

Want to write a blog post or tutorial

That would be amazing! Reach out to the Chakra UI Vue core team here: https://discord.gg/dQHfcWF. We would love to support you any way we can.

Want to help improve the docs?

By default, the GitHub REST API has an anonymous user rate limit. This can be hit during heavy local docs development if the server is frequently restarted.

Creating a GitHub token and storing it as the GITHUB_TOKEN environment variable allows the user to avoid the limit.

Visit https://github.com/settings/tokens/new?description=Chakra+website+development to create a new personal access token. After creating the token, be sure to copy the token string to your clipboard.

You'll then run the following command in the terminal that you'll start the docs from:

export GITHUB_TOKEN=<PASTE YOUR TOKEN HERE>

License

By contributing your code to the chakra-ui-vue GitHub repository, you agree to license your contribution under the MIT license.