@bigbinary/neeto-approvals-frontend 0.0.2
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 +43 -0
- package/dist/index.cjs.js +8031 -0
- package/dist/index.cjs.js.map +1 -0
- package/dist/index.esm.js +7992 -0
- package/dist/index.esm.js.map +1 -0
- package/package.json +164 -0
package/README.md
ADDED
|
@@ -0,0 +1,43 @@
|
|
|
1
|
+
# @bigbinary/neeto-approvals-frontend
|
|
2
|
+
|
|
3
|
+
neetoApprovals is a library that manages approvals across neeto products.
|
|
4
|
+
|
|
5
|
+
## Installation
|
|
6
|
+
|
|
7
|
+
1. **neetoApprovals** has a few peer dependencies that are required for the proper
|
|
8
|
+
functioning of the package. Install all the peer dependencies using the below
|
|
9
|
+
command:
|
|
10
|
+
|
|
11
|
+
```zsh
|
|
12
|
+
yarn add @bigbinary/neeto-icons@1.8.46 @bigbinary/neetoui@4.1.33 axios@1.2.1 classnames@2.3.2 formik@2.2.9 ramda@0.28.0 react-router-dom@5.3.3 react-toastify@8.2.0 react-query@3.39.2 yup@0.32.11
|
|
13
|
+
```
|
|
14
|
+
|
|
15
|
+
2. Now install the latest **neetoApprovals** package using the below command:
|
|
16
|
+
|
|
17
|
+
```zsh
|
|
18
|
+
yarn add @bigbinary/neeto-approvals-frontend
|
|
19
|
+
```
|
|
20
|
+
|
|
21
|
+
## Usage
|
|
22
|
+
WIP
|
|
23
|
+
|
|
24
|
+
## Development
|
|
25
|
+
|
|
26
|
+
1. Install all the dependencies by executing the following command
|
|
27
|
+
|
|
28
|
+
```zsh
|
|
29
|
+
yarn install
|
|
30
|
+
```
|
|
31
|
+
|
|
32
|
+
2. See the changes in the example app by executing the following command:
|
|
33
|
+
|
|
34
|
+
```zsh
|
|
35
|
+
yarn dev
|
|
36
|
+
```
|
|
37
|
+
|
|
38
|
+
## Building
|
|
39
|
+
|
|
40
|
+
The neetoApprovals package gets published to NPM only when we add the `release` label to the PR.
|
|
41
|
+
By default the `release` label will bump the patch version. If you want to release a minor or major version,
|
|
42
|
+
then along with the `release` label, add the `minor` or `major` label as well.
|
|
43
|
+
You can checkout the `publish` workflow in GitHub Actions to get a live update.
|