Conversation
The existing `README.md` "Quick Example" was passing the direct array response of `encrypt` into `decrypt`. This correctly updates the example to show the actual result array and usage of `ReversibleCryptoMetadataDTO` which is realistic and aligned with the API. Co-authored-by: Maatify <130119162+Maatify@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
1 participant
Aligned the code in the Quick Example section of the
README.mdto properly utilize the ReversibleCryptoMetadataDTO to build up the IV and tag properties. It now realistically depicts how an engineer is supposed to interface with the Reversible Crypto Service.PR created automatically by Jules for task 14670588458382688610 started by @Maatify