Running list of features required by ETHworks

[rzadp]

Features

• [x] Get a list of known contracts
• [ ] Invite a member (known contact) to a party using his public key, without the passcode flow
• [x] Unsubscribe/leave party
• [x] Parallel invitations
• [ ] Testing framework to test all of complex interactions without UX

Next

• [ ] Getting roles of members, assigning roles to members

Issues

• [ ] Errors with party (un)subscribing https://github.com/dxos/halo/issues/16
• [x] Multiple, parallel invitations are not working https://github.com/dxos/halo/issues/13
• [ ] Add roles https://github.com/dxos/halo/issues/17

[chriswaclawek]

@dboreham @telackey note addition of “ 6. Testing framework to test all of complex interactions without UX”

[telackey]

2. in @dxos/party-manager@1.0.1-beta.19+
3. in @dxos/party-manager@1.0.1-beta.18+

[telackey]

@rzadp I added a new test case here: https://github.com/dxos/halo/blob/master/packages/party-manager/src/party-manager-parties.test.js#L64

It is narrowly scoped at substituting a publicKey-authorized invitation for a PIN-authorized one and covers what each end needs to do to create, accept, and validate the invitation.

Just to be clear, this doesn't cover out-of-band communication of the invitation details or anything about offline invitations. See: https://github.com/dxos/halo/issues/18