You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The uncertain thing is naming and structure of aries_vcx_core, but it will be definitely renamed
I've slightly renamed some of the did methods crates, eg did_resolver_sov to just did_sov
Not sure If I haven't misplaced public_key or did_key
The main idea is to clearly separate aries components and other reusable components (even outside of ariex context) such as did_document, did, perhaps whather aries_vcx_core will endup being called
The text was updated successfully, but these errors were encountered:
Moving here the discussion from PR #998
Current structure proposal:
.github
docs
aries
aries_vcx_core (rename to something else)
did_document
did
tools
The uncertain thing is naming and structure of
aries_vcx_core
, but it will be definitely renamedI've slightly renamed some of the did methods crates, eg
did_resolver_sov
to justdid_sov
Not sure If I haven't misplaced
public_key
ordid_key
The main idea is to clearly separate aries components and other reusable components (even outside of ariex context) such as
did_document
,did
, perhaps whatheraries_vcx_core
will endup being calledThe text was updated successfully, but these errors were encountered: