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
Current didcomm-jvm implementation treats please_ack header as a boolean and ack header as a string.
According to the current specs both headers should be treated as array of strings (IDs).
Why
Because of that, original ack and please_ack headers cannot be used in current dependent applications with respect to current specification
Success Criteria
ack and please_ack headers treated as array of strings.
Additional info
Implementation can be found in Message class
data class Message(
...
val pleaseAck: Boolean?,
val ack: String?,
...
)
The text was updated successfully, but these errors were encountered:
What
Current didcomm-jvm implementation treats
please_ack
header as a boolean andack
header as a string.According to the current specs both headers should be treated as array of strings (IDs).
Why
Because of that, original
ack
andplease_ack
headers cannot be used in current dependent applications with respect to current specificationSuccess Criteria
ack
andplease_ack
headers treated as array of strings.Additional info
Implementation can be found in
Message
classThe text was updated successfully, but these errors were encountered: