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

test: enable tests #14

Closed
wants to merge 126 commits into from
Closed

test: enable tests #14

wants to merge 126 commits into from

Conversation

YoussefAWasfy
Copy link
Collaborator

No description provided.

- bs58
- sha2
- serde-enum-str
- uuid
SSL Network server added
Config Management added
Stats starting to be added
Basic structure of REST handling starting to be put in place
Inbound message handling started
Refactoring of message handling - about to fork
Now need to create an enum of envelope types to simplify the unpacking process.
Likely going to regret removing lifetimes and add back later
Trade-off on speed/performance of not copying data vs complexity of lifetimes
- Implemented Envelope enum so we know what type the message is

All didcomm-rust tests are working in this version.
Refactor: SecretsResolver uses &[String] instead of &Vec<String>
Created MetaEnvelope so we can keep associated data together
Refactored the way we handle DID resolution (still ugly)

unpacking an inbound message now works, but does nothing
Added ability to update DID and Secrets Resolevrs inside the unpack
- added allow for clippy::single_component_path_imports for examples
     - gets rid of a compiler warning that is not a problem
Fixed message_inbound so it works with updated didcomm crate
Added file structure for protocols including ping protocol
Need to now implement ability to write to the database
and for the client to poll looking for the response message.

Currently it cheats and returns the response message in the body of the HTTP response.
Still need to implement database storage and retrieval of trust-ping messages.
iharvarauka and others added 25 commits September 10, 2024 12:05
…the ATM-SDK

* pack_encrypted() - encrypted and optionally signed message
* pack_signed() - plaintext and signed message
* pack_plaintext() - plaintext! not encrypted, not signed
* unpack() - unpacks any format DIDComm message
* NOTE: You are responsible for sending this message to the mediator as a separate step.
*        HTTP(S)   : Call atm.send.didcomm_message(&message, true|false)
*        WebSocket : Call atm.ws-send_didcomm_message(&message, &message_id)
- added did-peer as a dev-dependency in mediator
This allows for the same DIDCache to be utilised by
the application outside of ATM and within ATM.

If you don't specify an external cache, then a local internal cache wil
be automatically created.

2. Added DID Resolevr Cache configuation to mediator

Allows for tuning of the DID resolver cache in the mediator
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants