Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: introduce DynamicExtrinsic type for compatibility #32

Merged
merged 10 commits into from
Aug 20, 2024

Conversation

freddyli7
Copy link

Description

Related Issue Or Context

Closes: #

How Has This Been Tested? Testing details.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation

Checklist:

  • I have commented my code, particularly in hard-to-understand areas.
  • I have ensured that all acceptance criteria (or expected behavior) from issue are met
  • I have updated the documentation locally and in chainbridge-docs.
  • I have added tests to cover my changes.
  • I have ensured that all the checks are passing and green, I've signed the CLA bot

@freddyli7 freddyli7 changed the title Freddy/latest gsrpc test feat: add DynamicExtrinsic type for compatibility Aug 19, 2024
@freddyli7 freddyli7 changed the title feat: add DynamicExtrinsic type for compatibility feat: introduce DynamicExtrinsic type for compatibility Aug 19, 2024
Copy link

Go Test coverage is 54.1 %\ ✨ ✨ ✨

@freddyli7 freddyli7 marked this pull request as ready for review August 19, 2024 18:56
@mpetrun5
Copy link

If this is working properly now we can submit it to the main branch.

@freddyli7 freddyli7 merged commit 2d403fe into fix/check-metadata-hash Aug 20, 2024
5 checks passed
@freddyli7 freddyli7 deleted the freddy/latest-GSRPC-test branch August 20, 2024 14:27
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.

2 participants