Skip to content

Commit 2e1accb

Browse files
committed
chore: reamde
1 parent fe86f77 commit 2e1accb

File tree

1 file changed

+32
-0
lines changed

1 file changed

+32
-0
lines changed

packages/gesturehandler/README.md

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,10 @@
5050
* [Demos](#demos)
5151
* [Contributing](#contributing)
5252
* [Update repo ](#update-repo-)
53+
* [Update readme ](#update-readme-)
54+
* [Update doc ](#update-doc-)
5355
* [Publish](#publish)
56+
* [modifying submodules](#modifying-submodules)
5457
* [Questions](#questions)
5558

5659

@@ -141,6 +144,11 @@ The source is based on the source code by [Krzysztof Magiera](https://github.com
141144

142145
### Repo Setup
143146

147+
The repo uses submodules. If you did not clone with ` --recursive` then you need to call
148+
```
149+
git submodule update --init
150+
```
151+
144152
The package manager used to install and link dependencies must be `pnpm` or `yarn`. `npm` wont work.
145153

146154
To develop and test:
@@ -156,6 +164,7 @@ To start the interactive menu, run `npm start` (or `yarn start` or `pnpm start`)
156164
```bash
157165
npm run build.all
158166
```
167+
WARNING: it seems `yarn build.all` wont always work (not finding binaries in `node_modules/.bin`) which is why the doc explicitly uses `npm run`
159168

160169
### Demos
161170

@@ -165,6 +174,10 @@ npm run demo.[ng|react|svelte|vue].[ios|android]
165174
npm run demo.svelte.ios # Example
166175
```
167176

177+
Demo setup is a bit special in the sense that if you want to modify/add demos you dont work directly in `demo-[ng|react|svelte|vue]`
178+
Instead you work in `demo-snippets/[ng|react|svelte|vue]`
179+
You can start from the `install.ts` of each flavor to see how to register new demos
180+
168181

169182
[](#contributing)
170183

@@ -188,6 +201,16 @@ npm run sync
188201
```
189202
Then you can run `yarn|pnpm`, commit changed files if any
190203

204+
### Update readme
205+
```bash
206+
npm run readme
207+
```
208+
209+
### Update doc
210+
```bash
211+
npm run doc
212+
```
213+
191214
### Publish
192215

193216
The publishing is completely handled by `lerna` (you can add `-- --bump major` to force a major release)
@@ -196,6 +219,15 @@ Simply run
196219
npm run publish
197220
```
198221

222+
### modifying submodules
223+
224+
The repo uses https:// for submodules which means you won't be able to push directly into the submodules.
225+
One easy solution is t modify `~/.gitconfig` and add
226+
```
227+
[url "ssh://[email protected]/"]
228+
pushInsteadOf = https://github.com/
229+
```
230+
199231

200232
[](#questions)
201233

0 commit comments

Comments
 (0)