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

move overloads of execute to @libsql/core/api (because its part of the public API) && add CONTRIBUTING.md #261

Merged
merged 11 commits into from
Sep 25, 2024
Prev Previous commit
Next Next commit
better instructions for contribution
DaBigBlob committed Sep 25, 2024
commit 92ea842b4b3bce8b971ce9957f8c53c6492a41af
16 changes: 8 additions & 8 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -1,13 +1,13 @@
# Prerequisites

- have `npm` installed and in PATH
- have `git` installed and in PATH
- Have `npm` installed and in PATH
- Have `git` installed and in PATH

# Setting up the repo for contributing
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't think the \*nix is relevant.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

i dont use windows (or haiku or whatever) so i have no knowledge of non *nix
"... for *nix" does not mean not for windows. it simply means that this works for *nix. and does not specify anything for windows, etc

Copy link
Contributor

Choose a reason for hiding this comment

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

I agree, I don't think that the *nix is relevant. I don't use windows either but a quick search and from my experience just mentioning the cd is enough.

Below is a rewrite of your instructions with some suggestions to improve clarity. Feel free to copy it completely or update what you think is relevant. I wanted to make sure that each step has a clear description and associated action.

Suggested change
# Setting up the repo for contributing
# Setting up the repo for contributing
- Clone this repository: `git clone https://github.com/tursodatabase/libsql-client-ts`
- Change the current working directory to the cloned repository: `cd libsql-client-ts`
- Install dependencies: `npm i`
- Change the current working directory to `libsql-core`'s workspace: `cd packages/libsql-core`
- Built the core package: `npm run build`
- Go back to the root directory to start making changes: `cd ../..`


- clone this repo (`git clone <this repo's url> libsql-client-ts` on \*nix)
- change the current working directory to the cloned repo (`cd libsql-client-ts` on \*nix)
- `npm i`
- change the current working directory to `libsql-core`'s workspace (`cd packages/libsql-core` on \*nix)
- build it (`npm run build` on \*nix)
- finally change back to base directory and start experimenting! (`cd ../..` on \*nix)
- Clone this repository: `git clone https://github.com/tursodatabase/libsql-client-ts`
- Change the current working directory to the cloned repository: `cd libsql-client-ts`
- Install dependencies: `npm i`
- Change the current working directory to `libsql-core`'s workspace: `cd packages/libsql-core`
- Built the core package: `npm run build`
- Go back to the root directory to start making changes: `cd ../..`