Pierre Dommerc
7ff043d8df
* wip * updated gateways 'sign' command * in-wallet verification of mix bonding signature * changed signature of vesting contract trait method * updated wallet bonding endpoints * tauri commands for generating signing payloads * renamed signer to sender * verifying new signatures in the contract * fixed existing mixnet unit tests * unit tests for invalid signatures * fixed other usages of MessageSignature + FromStr * using base58-encoded serialization * removed owner-signature from details response * added ability to construct bonding payloads via nym-cli * removed signature from bonding payload args * moved 'message_type' from 'ContractMessageContent' to 'SignableMessage' * refactor(wallet-rust): rename owner_signature args * feat(wallet-bonding): handle user signature * feat(wallet-bonding): fix bonding * feat(wallet-bonding): fix lint issue * feat(wallet-bonding): ui adjustment * make the location field mandatory for payload signing * feat(wallet-bonding): remove ownersignature field, remove dead code --------- Co-authored-by: Jędrzej Stuczyński <jedrzej.stuczynski@gmail.com> Co-authored-by: Tommy Verrall <tommyvez@protonmail.com>
Nym Typescript (and Javascript) packages
This directory has shared Typescript (and Javascript) libraries using yarn workspaces.
Why ts-packages?
Naming stuff is hard. The ts- part means Typescript, because this monorepo also contains Rust crates. So we needed some way to indicate: "put your Typescript here".
Now you know! So, please, put your Typescript here. And your Javascript.
How does it work?
In the root of this repository is package.json that specifies an array of globs for packages that are shared:
{
"name": "@nymproject/nymsphere",
"version": "1.0.0",
"private": true,
"license": "Apache 2.0",
"workspaces": ["ts-packages/*", "nym-wallet"] <-------
}
There are some caveats:
- this only works with
yarnand notnpm yarncreates a singlenode_modulesin the root for shared dependencies- packages that use shared packages, need to be in a path specified in
workspaces - local packages take precedence over published packages on
npm
Building
From the root of the repository run:
yarn
yarn build
This will build all libraries.
Now you can try out react-webpack-with-theme-example by running:
cd ts-packages/react-webpack-with-theme-example
yarn start
Our React components have a Storybook in react-components:
cd ts-packages/react-components
yarn storybook
Development
Watch mode is available in some packages with yarn watch.
See mui-theme for an example.