AbsaOSS / AbsaOSS/vcxagencynode

Handle both legacy and current @type values in forward messages

未关闭
#119 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
主要语言
JavaScript
星标
23
派生
8
PR 合并指标
30 天内没有已合并 PR

描述

Currently, agency expects and uses legacy `@type` attribute for forward messages:
```
did:sov:BzCbsNYhMrjHiqZDTUASHg;spec/routing/1.0/forward
```

However, as per aries spec (see [here](https://github.com/hyperledger/aries-rfcs/blob/08653f21a489bf4717b54e4d7fd2d0bdfe6b4d1a/concepts/0020-message-types/README.md#aries-core-message-namespace)), a different value should be used for the attribute:
```
https://didcomm.org/routing/1.0/forward
```

Agency should support both formats for some time in order to remain backwards compatible.

Analogous change was already implemented in aries-vcx (see [here](https://github.com/hyperledger/aries-vcx/pull/341)).

贡献指南

这个仓库没有索引到贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。