@bigbinary/neeto-webhooks-frontend 1.5.3 → 1.5.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -1,101 +1,21 @@
1
- # @bigbinary/neeto-webhooks-frontend
2
1
 
3
- neetoWebhooks is the library that manages webhooks across neeto products.
2
+ [![BuildStatus](https://neeto-engineering.neetoci.com/badges/neeto-webhooks-nano/workflows/default.svg)](https://neeto-engineering.neetoci.com/projects/neeto-webhooks-nano)
4
3
 
5
- ## Installation
4
+ # neeto-webhooks-nano
5
+ Nano to manage webhooks on neeto applications.
6
6
 
7
- ```bash
8
- yarn add "@bigbinary/neeto-webhooks-frontend@1.4.0"
9
- ```
10
7
 
11
- \*_neetoWebhooks_ has a few peer dependencies that are required for the proper
12
- functioning of the package. Install all the peer dependencies using the below
13
- command:
8
+ # Local Development Setup
14
9
 
15
- ```bash
16
- yarn add @bigbinary/neetoui @bigbinary/neeto-icons axios@0.27.2 classnames@2.3.1 dayjs@1.11.1 formik@2.2.9 ramda@0.28.0 react-router-dom@5.3.4 react-toastify@9.0.1 yup@0.32.11
17
- ```
10
+ 1. Setup
11
+ [Instructions](https://github.com/bigbinary/neeto-engineering/tree/main/Local-Development-Setup).
18
12
 
19
- ## Usage
13
+ 2. Run `yarn build` to bundle the app.
20
14
 
21
- ```jsx
22
- import React from "react";
15
+ 3. Visit http://spinkart.lvh.me:9100 and login with email `oliver@example.com`
16
+ and password `welcome`.
23
17
 
24
- import { NeetoWebhooks } from "@bigbinary/webhooks-frontend";
25
- import routes from "./routes";
18
+ # Publish instructions
26
19
 
27
- const App = () => (
28
- <BrowserRouter>
29
- <Switch>
30
- <Route path={routes.meeting.webhooks}>
31
- <NeetoWebhooks entityType="Meeting" />
32
- </Route>
33
- </Switch>
34
- <ToastContainer />
35
- </BrowserRouter>
36
- );
37
- export default App;
38
- ```
39
-
40
- ### 1. NeetoWebhooks
41
-
42
- This component is used to show, add, edit and delete webhooks
43
-
44
- ##### Props
45
-
46
- 1. **entityType:** class name of the entity item connecting to the webhooks,
47
- i.e. Model name as a string
48
-
49
- ## Development
50
-
51
- 1. Install all the dependencies by executing the following command
52
-
53
- ```sh
54
- yarn install
55
- ```
56
-
57
- 2. See the changes in the example app by executing the following command (from
58
- existing seed data):
59
-
60
- ```zsh
61
- yarn dev
62
- ```
63
-
64
- or to see the changes by running the Rails Engine in parallel, execute the
65
- following command:
66
-
67
- ```sh
68
- yarn start
69
- ```
70
-
71
- In order to run the application you need to run the Rails server of the
72
- neetoWebhooks engine's dummy application as well. This is necessary to make sure
73
- that all the APIs and React Query hooks are working as per the requirement.
74
-
75
- ```bash
76
- git clone https://github.com/bigbinary/neeto-webhooks-engine.git
77
- ./test/dummy/bin/setup
78
- rails server
79
- ```
80
-
81
- # Building and releasing.
82
-
83
- The `@bigbinary/neeto-webhooks-frontend` package gets published to NPM when we
84
- merge a PR with `patch`, `minor` or `major` label to the `main` branch. The
85
- `patch` label is used for bug fixes, `minor` label is used for new features and
86
- `major` label is used for breaking changes. You can checkout the
87
- `Create and publish releases` workflow in GitHub Actions to get a live update.
88
-
89
- In case if you missed to add the label, you can manually publish the package.
90
- For that first you need to create a PR to update the version number in the
91
- `package.json` file and merge it to the `main` branch. After merging the PR, you
92
- need to create a
93
- [new github release](https://github.com/bigbinary/neeto-webhooks-frontend/releases/new)
94
- from main branch. Whenever a new release is created with a new version number,
95
- the github actions will automatically publish the built package to npm. You can
96
- checkout the `Publish to npm` workflow in GitHub Actions to get a live update.
97
-
98
- Please note that before publishing the package, you need to verify the
99
- functionality in some of the neeto web-apps locally using `yalc` package
100
- manager. The usage of yalc is explained in this video:
101
- https://youtu.be/QBiYGP0Rhe0
20
+ 1. [Engine and package installation](./docs/engine-and-package-installation.md)
21
+ 2. [Building and releasing](./docs/building-and-releasing.md)