Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: update CONTRIBUTING.md #2935

Open
wants to merge 16 commits into
base: main
Choose a base branch
from

Conversation

sukvvon
Copy link
Contributor

@sukvvon sukvvon commented Jan 15, 2025

Summary

  • Update CONTRIBUTING.md

Check List

  • pnpm run fix:format for formatting code and docs

Copy link

vercel bot commented Jan 15, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
jotai ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 25, 2025 5:02pm

Copy link

codesandbox-ci bot commented Jan 15, 2025

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Copy link

pkg-pr-new bot commented Jan 15, 2025

Open in Stackblitz

More templates

npm i https://pkg.pr.new/jotai@2935

commit: 1e0dce7

Copy link

github-actions bot commented Jan 15, 2025

LiveCodes Preview in LiveCodes

Latest commit: 1e0dce7
Last updated: Jan 25, 2025 5:01pm (UTC)

Playground Link
React demo https://livecodes.io?x=id/CM3TLJKDB

See documentations for usage instructions.

@sukvvon
Copy link
Contributor Author

sukvvon commented Jan 15, 2025

@dai-shi

I think we don't need to use yalc and it's fine only using pnpm link, because before use yalc, we need to install it.
Would you want to use yalc?

@dai-shi
Copy link
Member

dai-shi commented Jan 15, 2025

Thanks for opening up the suggestion.

CONTRIBUTING.md isn't well maintained across three repos. So, it's a good chance to overhaul it.

Let's have two parts. The first part is common part that is same for all zustand/jotai/valtio. The second part is specific to each lib.

What would be your suggestion if you were to write it from scratch?

@sukvvon
Copy link
Contributor Author

sukvvon commented Jan 15, 2025

@dai-shi

Thanks for opening up the suggestion.

CONTRIBUTING.md isn't well maintained across three repos. So, it's a good chance to overhaul it.

Let's have two parts. The first part is common part that is same for all zustand/jotai/valtio. The second part is specific to each lib.

What would be your suggestion if you were to write it from scratch?

The first part sounds good. I think we can combine the best practices of both zustand and jotai. I believe it’s important to keep it concise and clear when writing.

@dai-shi
Copy link
Member

dai-shi commented Jan 15, 2025

Yeah, we didn't have one in valtio.

@sukvvon
Copy link
Contributor Author

sukvvon commented Jan 15, 2025

@dai-shi

Yeah, we didn't have one in valtio.

Yeah, i saw valtio doesn't have it

I'll update CONTRIBUTING.md with the combined zustand and jotai in this PR, then i'll create the same PR in valtio and zustand

@sukvvon sukvvon marked this pull request as draft January 16, 2025 02:12
@sukvvon sukvvon changed the title docs(CONTRIBUTING.md): clarify used scripts docs: updaet CONTRIBUTING.md Jan 16, 2025
@sukvvon sukvvon changed the title docs: updaet CONTRIBUTING.md docs: update CONTRIBUTING.md Jan 16, 2025
@sukvvon sukvvon marked this pull request as ready for review January 17, 2025 01:43
@dai-shi
Copy link
Member

dai-shi commented Jan 17, 2025

Is it possible to have two sections for part 1 and part 2 more explicitly?

Something like:

# Contributing

## General Guideline

...

## Project-specific Guideline

...

By this way, the review gets easier. The more we put guide in part 1, the better and easier to maintain.

@sukvvon sukvvon marked this pull request as draft January 17, 2025 06:37
@sukvvon sukvvon marked this pull request as ready for review January 21, 2025 12:28
Copy link
Member

@dai-shi dai-shi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't look into all of them, but here are some comments.

CONTRIBUTING.md Outdated Show resolved Hide resolved
CONTRIBUTING.md Outdated Show resolved Hide resolved
CONTRIBUTING.md Outdated Show resolved Hide resolved
@sukvvon sukvvon requested a review from dai-shi January 23, 2025 01:24
CONTRIBUTING.md Outdated Show resolved Hide resolved
CONTRIBUTING.md Outdated Show resolved Hide resolved
Co-authored-by: Daishi Kato <[email protected]>
CONTRIBUTING.md Outdated

1. Install dependencies by running `pnpm install`.
2. Create failing tests for your fix or new feature in the `tests` folder
2. Create failing tests for your fix or new feature in the [`tests`](./tests/) folder. (e.g., `cd tests`)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've never done cd tests. Do you do it?

Copy link
Contributor Author

@sukvvon sukvvon Jan 24, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dai-shi

Create failing tests for your fix or new feature

The existing document already specifies performing tasks like the one mentioned above, and since the test path is also mentioned in the document, I added the cd tests command. Would you like me to remove the cd tests command?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I assume most devs open tests/* files from the project root.

Copy link
Contributor Author

@sukvvon sukvvon Jan 24, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dai-shi Yeah, so i added introducing about how to move tests folder from project root.

Copy link
Contributor Author

@sukvvon sukvvon Jan 24, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dai-shi

Yeah, I assume most devs open tests/* files from the project root.

Do you want to remove all of cd command part?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All except for cd website as it's required to install node modules.

Copy link
Member

@dai-shi dai-shi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unfortunately, I can't think of any ways to make urls in common across projects.

CONTRIBUTING.md Outdated Show resolved Hide resolved
CONTRIBUTING.md Outdated Show resolved Hide resolved
CONTRIBUTING.md Outdated Show resolved Hide resolved
CONTRIBUTING.md Outdated Show resolved Hide resolved
CONTRIBUTING.md Outdated Show resolved Hide resolved
sukvvon and others added 5 commits January 24, 2025 17:09
Co-authored-by: Daishi Kato <[email protected]>
Co-authored-by: Daishi Kato <[email protected]>
Co-authored-by: Daishi Kato <[email protected]>
Co-authored-by: Daishi Kato <[email protected]>
Co-authored-by: Daishi Kato <[email protected]>
Copy link
Member

@dai-shi dai-shi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM
Let's do this in other two repos.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants