Mokhtar Naamani f4cb727dec bump types and metadata npm package version | 2 lat temu | |
---|---|---|
.. | ||
doc | 2 lat temu | |
proto | 2 lat temu | |
scripts | 3 lat temu | |
src | 2 lat temu | |
test | 3 lat temu | |
.eslintignore | 3 lat temu | |
.eslintrc.js | 3 lat temu | |
.gitignore | 3 lat temu | |
.prettierignore | 3 lat temu | |
README.md | 3 lat temu | |
compile.sh | 3 lat temu | |
doc-appendix.md | 3 lat temu | |
generate-md-doc.sh | 3 lat temu | |
package.json | 2 lat temu | |
tsconfig.json | 2 lat temu |
This package contains protobuf message definitions compiled to Javascript/Typescript used for creating and updating various metadata blobs in Joystream.
Documented in doc folder
For our usecase we wish to re-use same message to create and update subset of fields. For this reason we need the explicit information about wether a field has been set or not and this is only possible with proto v2.
Background: required/optional feilds are deprecated in proto v3
The custom Joystream types such as License have helper methods to construct pre-defined well known values.
Best place to look at are the tests specs
We use simple ISO_639-1 code representation for Language. useful npm package https://www.npmjs.com/package/iso-639-1
Building will compile the protofiles using protobufjs and build the library from source.
pre-requisists for generating documentation:
protoc-gen-doc to generate docs
yarn && yarn build
yarn generate-docs
yarn test