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
Currently, it is possible to define a V2 package that changes a template's key definition wrt V1. According to the design, at runtime the engine/ledger should check that the key evaluates to the same value with both versions, but that isn't the case with queryContractKey/queryContractId/fetchByKey/exerciseByKey/exerciseByKeyCmd`.
Currently, it is possible to define a V2 package that changes a template's key definition wrt V1. According to the design, at runtime the engine/ledger should check that the key evaluates to the same value with both versions, but that isn't the case with
queryContractKey
/
queryContractId/
fetchByKey/
exerciseByKey/
exerciseByKeyCmd`.Test cases PRs:
main-2.x
) [Upgrades testing] Add cases for unchanged key type with changed key expression #19897main
) [Forward-port][Upgrades testing] Add cases for unchanged key type with changed key expression #19947The text was updated successfully, but these errors were encountered: