-
-
Notifications
You must be signed in to change notification settings - Fork 639
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
base: main
Are you sure you want to change the base?
docs: update CONTRIBUTING.md #2935
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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. |
commit: |
Preview in LiveCodesLatest commit: 1e0dce7
See documentations for usage instructions. |
I think we don't need to use |
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. |
Yeah, we didn't have one in valtio. |
Yeah, i saw valtio doesn't have it I'll update |
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. |
There was a problem hiding this 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.
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`) |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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?
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
Do you want to remove all of cd
command part?
There was a problem hiding this comment.
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.
There was a problem hiding this 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.
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]>
There was a problem hiding this 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.
Summary
CONTRIBUTING.md
Check List
pnpm run fix:format
for formatting code and docs