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 reason why I thought prefixing cached: was incorrect was because of this commen tmade in 2022 : #64 (comment)
The Issue:
Java REPL
The first line shows .getAtKeys() working (where it would ultimately use atKey.toString())
The second line shows a raw atProtocol scan where cached: is shown (because that is how the protocol behaves)
But there's no immediate need for the Java SDK, I assume, so maybe this is something to backlog? @gkc What do you think? Maybe it could be a good starting intern ticket
I don't think this issue is a pressing issue, which is why I'm bumping it down to P3 as well
The reason why I thought prefixing cached: was incorrect was because of this commen tmade in 2022 : #64 (comment)
The Issue:
Java REPL
The first line shows .getAtKeys() working (where it would ultimately use atKey.toString())
The second line shows a raw atProtocol scan where cached: is shown (because that is how the protocol behaves)
Correct behaviour should be atKey.toString() should prefix
cached:
just like the raw scan.The text was updated successfully, but these errors were encountered: