feat(types/collections): add LegacyDec collection value

[johnletey]

Description

Closes: #XXXX

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• included the correct type prefix in the PR title, you can find examples of the prefixes below:
• confirmed ! in the type prefix if API or client breaking change
• targeted the correct branch (see PR Targeting)
• provided a link to the relevant issue or specification
• reviewed "Files changed" and left comments if necessary
• included the necessary unit and integration tests
• added a changelog entry to CHANGELOG.md
• updated the relevant documentation or specification, including comments for documenting Go code
• confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

Please see Pull Request Reviewer section in the contributing guide for more information on how to review a pull request.

I have...

• confirmed the correct type prefix in the PR title
• confirmed all author checklist items have been addressed
• reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

Summary by CodeRabbit

• New Features
  • Introduced support for legacy decimal values, enhancing compatibility with existing data formats.
  • Added methods for encoding, decoding, and JSON handling of legacy decimal values.

[coderabbitai]

Walkthrough

Walkthrough

The changes introduce a new ValueCodec specifically for handling math.LegacyDec values, named LegacyDecValue. This includes the creation of the legacyDecValueCodec struct, which implements methods for encoding, decoding, and JSON handling of math.LegacyDec instances. Additionally, a constant representing the type in string form is added. These modifications enhance the collections package's ability to support legacy decimal values.

Changes

Files	Change Summary
types/collections.go	Added LegacyDecValue codec, including legacyDecValueCodec struct and methods for encoding, decoding, and JSON handling of math.LegacyDec. Added constant LegacyDec for type representation.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant LegacyDecValueCodec
    participant MathLegacyDec

    Client->>LegacyDecValueCodec: Encode(math.LegacyDec)
    LegacyDecValueCodec->>MathLegacyDec: Convert to byte representation
    MathLegacyDec-->>LegacyDecValueCodec: Byte data
    LegacyDecValueCodec-->>Client: Encoded byte data

    Client->>LegacyDecValueCodec: Decode(byte data)
    LegacyDecValueCodec->>MathLegacyDec: Convert byte data to math.LegacyDec
    MathLegacyDec-->>LegacyDecValueCodec: LegacyDec instance
    LegacyDecValueCodec-->>Client: Decoded math.LegacyDec instance

Loading

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[testinginprod]

LGTM

[tac0turtle]

@johnletey can you lint and merge main then we can merge it

[johnletey]

@tac0turtle The linter doesn't seem to be related to this PR, should I still fix it?

[julienrbrt]

@tac0turtle The linter doesn't seem to be related to this PR, should I still fix it?

It should be fixed on main already

[johnletey]

@julienrbrt Looks like the test-system is failing, is it flaky?

[julienrbrt]

Shouldn't be but looks like it..