@covergo/covergo-sdk NPM

Usage

All query/mutation calls have a single parameter as an object that takes the following properties

{variables = {}, token = '', locale = "en", __debug = false, errorLocation = null}

The variables property must follow the inputTypes as defined in https://api.covergo.com/playground Name of the variable is name of the param.

Contributing

Commits

commit messages must follow our commit guidelines (based on Angular commit message conventions)

Commit Message Format

<type>(<scope>): <subject>
<BLANK LINE>
<body>
<BLANK LINE>
<footer>

The header is mandatory and the scope of the header is optional.

Any line of the commit message cannot be longer 100 characters! This allows the message to be easier to read on GitHub as well as in various git tools.

Revert

If the commit reverts a previous commit, it should begin with revert: , followed by the header of the reverted commit. In the body it should say: This reverts commit ., where the hash is the SHA of the commit being reverted.

Type

Must be one of the following:

feat: A new feature (creates a MINOR (feature) RELEASE unless there is a breaking change) fix: A bug fix (creates a PATCH RELEASE) docs: Documentation only changes style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc) refactor: A code change that neither fixes a bug nor adds a feature perf: A code change that improves performance test: Adding missing or correcting existing tests chore: Changes to the build process or auxiliary tools and libraries such as documentation generation Scope

The scope could be anything specifying place of the commit change. For example products, insurers, etc...

You can use * when the change affects more than a single scope.

Subject

The subject contains succinct description of the change:

use the imperative, present tense: "change" not "changed" nor "changes" don't capitalize first letter no dot (.) at the end Body

Just as in the subject, use the imperative, present tense: "change" not "changed" nor "changes". The body should include the motivation for the change and contrast this with previous behavior.

Footer

The footer should contain any information about Breaking Changes and is also the place to reference GitHub issues that this commit closes.

Breaking Changes should start with the word BREAKING CHANGE: with a space or two newlines. The rest of the commit message is then used for this.

Commits with breaking changes will automatically generate a MAJOR (breaking) RELEASE when pushed to master

Releasing a new version

Simply push to master and the package will be built tested and released. Commit logs will automatically generate the new version, release notes and changelog.md

cross-fetch

@infinitebrahmanuniverse/nolb-_cov @everything-registry/sub-chunk-201 @zalastax/nolb-_cov

4 years ago

5 years ago

5 years ago

5 years ago

5 years ago