-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #13 from vegaprotocol/feat/help
Add more helpful help
- Loading branch information
Showing
18 changed files
with
217 additions
and
38 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,4 @@ | ||
#!/bin/sh | ||
. "$(dirname "$0")/_/husky.sh" | ||
|
||
npm run lint -- --fix |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,5 @@ | ||
#!/bin/sh | ||
. "$(dirname "$0")/_/husky.sh" | ||
|
||
npm run test | ||
npm run lint |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,5 @@ | ||
# approbation | ||
Coverage matrix for [specifications](https://github.com/vegaprotocol/specs) | ||
Scripts for producing a coverage matrix for Vega [specifications](https://github.com/vegaprotocol/specs) | ||
|
||
## Specification file names | ||
Each protocol specification receives a sequence number when it is merged in to master. | ||
|
@@ -61,11 +61,39 @@ set of tests, to produce a coverage number | |
|
||
# Running these checks | ||
|
||
## v2.0.0 onwards | ||
_All_ checks take a `--specs` argument, which is a [glob](https://www.npmjs.com/package/glob) specifying the specification files to check. | ||
|
||
```bash | ||
npx @vegaprotocol/[email protected] check-codes --specs='./protocol/*.md' | ||
``` | ||
|
||
`check-references` also requires a `--tests` glob, specifying the tests to cross-reference with the `--specs`: | ||
|
||
```bash | ||
npx @vegaprotocol/[email protected] check-references --specs='./protocol/*.md' --tests='{./feature/*.feature,./system-tests/**/*.py}' | ||
``` | ||
|
||
This second example shows how to use globs to specify multiple paths containing tests. For more complex examples, check the | ||
[glob](https://www.npmjs.com/package/glob) documentation. | ||
|
||
### Defaults | ||
Default paths will be removed in v3.0.0, but exist in v2.0.0 for legacy support. If not specified, for `check-codes` & `check-filenames`: | ||
``` | ||
--specs='{./non-protocol-specs/**/*.md,./protocol/**/*.md}' | ||
``` | ||
|
||
And for `check-references`: | ||
``` | ||
npx @vegaprotocol/approbation check-references | ||
--specs='{./non-protocol-specs/**/*.md,./protocol/**/*.md}' | ||
--tests'{./qa-scenarios/**/*.{feature,py}}' | ||
``` | ||
|
||
# Development | ||
- Linting uses [standard](https://www.npmjs.com/package/standard) | ||
- Tests are run pre-push by [Husky](https://www.npmjs.com/package/husky) | ||
- Tags are pushed to npm | ||
|
||
# [License](./LICENSE) | ||
The Unlicense |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.