1.1.3 • Published 2 years ago

protocol-common v1.1.3

Weekly downloads
358
License
Apache-2.0
Repository
github
Last release
2 years ago

Using protocol-common

Protocol-common is a shared library of commonly used functions in protocol web services such as Aries-Guardianship-Agency.

Protocol-common is distributed through npm packages. Please use this npm package for your work.

Using protocol-common locally

If you'd like to use a local version of protocol-common instead of the version available through npm packages, we've added some handy scripts to help you do so. 1. In protocol-common, run the command npm run build:pack - This will compile your code into a dist/ directory and create a .tgz installable binary of protocol-common. - Note the path to the .tgz, this will be important for the next step! 2. In the project that will use protocol-common, run the command npm install <path to .tgz>. 3. Try it out!

Contributing to protocol-common

Getting Started

Typically, you'll need to update this repo when you want to change code that's shared among multiple services. 1. Create a branch. 2. Make your code changes. 3. (optional) Test your changes by using protocol-common locally with some other project that depends on it. 4. Update the "version" in package.json using Major.Minor.Patch semantic versioning. 5. Commit your change to the branch and create a new PR in Github. 6. Once approved and merged, CircleCI will automatically push an npm package with the version number you specified. 7. (optional) Update repos that consume protocol-common.

notes

github info
npm package how-to
using experimental features in packages

Library Documentation

Config Module data format

To use the ConfigModule, data needs to be passed in. The data needs to be a specific format. This is an example of that format.

{
     "default": {
       "SERVICE_NAME": "authservice"
     },
     "local": {
       "WALLET_SYNC_SERVICE_URL": "http://protocol-wallet-sync-service:3004",
       "IDENTITY_SERVICE_URL": "http://protocol-identity-service:8080",
       "IDENTITY_SERVICE_BACKEND": "ncratemplate",
       "MAX_LOG_LENGTH": 5000,
       "JAEGER_ENDPOINT": "http://jaeger:14268/api/traces",
       "JWT_EXPIRE_SECONDS": 36000,
       "TRACER": "",
       "RESTFUL_CLIENT_DELAY": 250,
       "RESTFUL_CLIENT_RETRY": 5
     },
     "dev": {},
     "qa": {},
     "sand": {},
     "prod": {}
   }

Migrating from 0.x.x to 1.x.x

Looking to use the latest version of protocol-common, but currently using an older version? See this doc for migration instructions.

1.1.1

2 years ago

1.1.3

2 years ago

1.1.2

2 years ago

1.1.0

2 years ago

1.0.2

2 years ago

1.0.3

2 years ago

1.0.1

2 years ago

1.0.0

2 years ago

0.1.50

2 years ago

0.1.49

3 years ago

0.1.48

3 years ago

0.1.47

3 years ago

0.1.44

3 years ago

0.1.45

3 years ago

0.1.46

3 years ago

0.1.43

3 years ago

0.1.42

3 years ago

0.1.41

3 years ago

0.1.40

3 years ago

0.1.39

3 years ago

0.1.37

3 years ago

0.1.38

3 years ago

0.1.36

3 years ago

0.1.35

3 years ago

0.1.34

3 years ago

0.1.32

3 years ago

0.1.33

3 years ago

0.1.31

3 years ago

0.1.30

3 years ago

0.1.29

3 years ago

0.1.27

3 years ago

0.1.28

3 years ago

0.1.26

3 years ago

0.1.25

3 years ago

0.1.23

3 years ago

0.1.24

3 years ago

0.1.22

3 years ago

0.1.21

3 years ago

0.1.20

4 years ago

0.1.19

4 years ago

0.1.18

4 years ago

0.1.17

4 years ago

0.1.16

4 years ago

0.1.15

4 years ago

0.1.14

4 years ago