Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HDK3 cleanup tasks #174

Closed
16 of 18 tasks
pospi opened this issue Sep 29, 2021 · 3 comments
Closed
16 of 18 tasks

HDK3 cleanup tasks #174

pospi opened this issue Sep 29, 2021 · 3 comments
Assignees
Labels

Comments

@pospi
Copy link
Member

pospi commented Sep 29, 2021

The migration to "Holochain RSM" is now complete-enough to be considered a new stable foundation to integrate from. A prototype version compatible with the previous HDK2 is tagged at the hdk-2.x branch.

Filing this issue to track cleanup jobs needed to finalise the task and achieve feature parity with the old version-

Blocking

Bugs

  • fix all EconomicResource container refs being cleared when only 1 is removed
  • ensure EconomicResource stage & state still work (they query the DHT for related records directly...)
  • ensure unit CRUD (and "anchored records") work as expected after changes to indexing architecture

Code clarity & maintainability / repo organisation / cleanup

Administration & documentation

  • publish Nodejs modules
    • @valueflows/vf-graphql-holochain
    • @vf-ui/graphql-client-holochain
  • Publish rust crates to crates.io #70
  • update workflow automation docs
  • update DNA Auth Resolver readme to point to final location of hdk_records lib, publish hc_zome_dna_auth_resolver crates

Work ahead and other things to note

@pospi pospi added the enhancement New feature or request label Sep 29, 2021
@pospi pospi added this to the Multi-DNA system core (MIP) milestone Sep 29, 2021
@pospi pospi self-assigned this Sep 29, 2021
@artbrock

This comment was marked as resolved.

@artbrock

This comment was marked as resolved.

@Connoropolous
Copy link
Contributor

anything in this epic issue that's not already done has an open issue for itself, and it feels like we've cleared this one and everything it captured! Closing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
No open projects
Status: Done
Development

No branches or pull requests

3 participants