Skip to content

Conversation

@fxamacker
Copy link
Owner

@fxamacker fxamacker commented Mar 24, 2023

Description

In JSON-CDC, sometimes cadence-type-id was encoded when it was just a "stringification" of other encoded data and not necessary to encode.

In CCF, we don't need to keep this inefficiency for the sake of compatibility.

Thanks @turbolent for spotting this!

Changes

Removed the inefficiency by removing unnecessary cadence-type-id from

  • restricted-type-value
  • restricted-type
  • function-value

Closes #68

In JSON-CDC, sometimes cadence-type-id was encoded when it was
just a "stringification" of other encoded data and not necessary to encode.

We don't need to keep this inefficiency for the sake of compatibility.

Remove the inefficiency by removing unnecessary cadence-type-id from
- restricted-type-value
- restricted-type
- function-value

Thanks @turbolent for spotting this!

Co-authored-by: Bastian Müller <bastian@axiomzen.co>
Copy link
Collaborator

@turbolent turbolent left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹

@fxamacker fxamacker merged commit 20e8520 into main Mar 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Remove unnecessary cadence-type-id

3 participants