-
-
Notifications
You must be signed in to change notification settings - Fork 328
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
Add contribution guide #527 #528
Add contribution guide #527 #528
Conversation
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.
Thanks @fflorent, this will be helpful! Could do with linking to it from the README, you have more precise information about building than it does.
.github/CONTRIBUTING.md
Outdated
- [translate](/documentation/translate.md) | ||
- [write tutorials and user documentation](https://github.com/gristlabs/grist-help) | ||
- [develop](/documentation/develop.md) | ||
- report issues or suggest enhancement (TODO) |
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.
TODO would be something like https://github.com/gristlabs/grist-core/issues/new?
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.
Probably.
Maybe to go further, an issue template could help ^^.
documentation/develop.md
Outdated
|
||
To setup your environment, you would need to install the following dependencies: | ||
- git | ||
- [nvm](https://github.com/nvm-sh/nvm/blob/master/README.md) |
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 use nvm personally but not sure if I'd put it as a requirement; could be a recommendation. The requirement is some version of node. The exact version to recommend is a bit fluid, I think I'd say 16 (though I think our tests and docker image may still use an older version), last I heard there was some awkwardness running browser tests with node 18 on osx m1 (cc @georgegevoian).
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 think 18 may work as long as it's not the arm64 version. The wrinkle with tests was that the version of chromedriver we currently use is stale (74) and doesn't support arm64, but I think when I tested a while back with newer versions most tests still passed, and the few that didn't were due to breaking changes in Selenium.
documentation/develop.md
Outdated
To setup your environment, you would need to install the following dependencies: | ||
- git | ||
- [nvm](https://github.com/nvm-sh/nvm/blob/master/README.md) | ||
- Firefox and/or Chromium to run the end-to-end (nbrowsers) 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.
Do you know if the tests can actually run with firefox? We used to test with both, but then slipped to just using one (chrome).
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 think so, I'll test that.
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.
And maybe just say "browser tests" instead of "(nbrowsers) 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.
Don't nbrowser tests cover not only the browser but also the back-end? I would keep the term end-to-end
tests, unless all of them don't require to run a server.
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.
Ok, end-to-end is fine. I was hoping to replace/eliminate nbrowsers
since it was a bit jargony (user won't know anything about the idiosyncratically named nbrowser
tests yet) and also the s
is maybe a bit confusing (the test target it is referring to is nbrowser
). How about just dropping (nbrowsers)
?
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.
Ah, I see it is already fixed 👍
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.
Ok, end-to-end is fine
If you're uncomfortable with naming them end-to-end, don't hesitate to tell me. I am not very confident on how to name them ^^
$ npm install -g yarn | ||
``` | ||
|
||
Now each time you want to load nodejs and yarn in your environment, just run the following command at grist-core root directory: |
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.
"at grist-core" -> "in the grist-core"
documentation/develop.md
Outdated
|
||
## Develop widgets | ||
|
||
TODO |
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.
If this is about custom widgets, it could point to https://github.com/gristlabs/grist-widget#readme or https://support.getgrist.com/widget-custom/ (though I do see looking at this now that neither is ideal).
6884955
to
d22c94d
Compare
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.
Thanks for your review @paulfitz, I changed some stuffs in accordance to your remarks.
documentation/develop.md
Outdated
To setup your environment, you would need to install the following dependencies: | ||
- git | ||
- [nvm](https://github.com/nvm-sh/nvm/blob/master/README.md) | ||
- Firefox and/or Chromium to run the end-to-end (nbrowsers) 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 think so, I'll test that.
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.
thanks for iterating, just a few small comments
documentation/develop.md
Outdated
|
||
#### Using nodejs | ||
|
||
You can also use nodejs installed in your system. To prevent instabilities, ensure that the `node --version` command a version equal or ulterior to the one in `.nvmrc`. |
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.
instabilities -> incompatibilities?
"command a version" -> "command reports a version"
I'd say "greater" rather than "ulterior"
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'd still vote against ulterior. Maybe "an equal or later/greater version"?
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.
Oopsi! I fix that, sorry for having missed that one.
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.
Almost there! Thanks for doing this (and for your patience).
documentation/develop.md
Outdated
To setup your environment, you would need to install the following dependencies: | ||
- git | ||
- [nvm](https://github.com/nvm-sh/nvm/blob/master/README.md) | ||
- Firefox and/or Chromium to run the end-to-end (nbrowsers) 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.
Ah, I see it is already fixed 👍
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.
Thanks @fflorent !
b4df9c4
to
5f3a0c5
Compare
@paulfitz Good! 😄 I rebased and squashed the commits for more clarity before you merge 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.
Thanks @fflorent !
Co-authored-by: Florent <[email protected]>
This PR fixes issue #527:
Feedback highly welcome :)