-
Notifications
You must be signed in to change notification settings - Fork 9
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: add bridge_amino and test #61
Conversation
}); | ||
|
||
await runAminoTest(msgClient, TEST_MSG_BRIDGE); | ||
}); | ||
}); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have tested this against redwood locally, including all negative tests I could think of, but we will need to implement #59 to run it in CI.
https://redwood.regen.aneka.io/txs/C70A43E236BAAB1B2DD2D352A03CBB72D8DF307EB7F03D61905315B26324C738
@@ -25,7 +25,7 @@ import { | |||
} from '../generated/regen/ecocredit/marketplace/v1/tx'; | |||
import { GeneratedType } from '@cosmjs/proto-signing'; | |||
|
|||
const ecocreditRegistry: Array<[string, GeneratedType]> = [ | |||
const ecocreditRegistry: ReadonlyArray<[string, GeneratedType]> = [ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ReadonlyArray
is more in line with the established convention for type registries.
packages/api/src/tx/msg.ts
Outdated
regenTypeRegistry.forEach(([key, value]) => { | ||
customRegistry.push([`/${key}`, value]); | ||
}); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not related to this PR, but why do we need this?
messageTypeRegistry.forEach
above is already registering all the types
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
deleted
@@ -37,9 +36,6 @@ export async function setupTxExtension( | |||
messageTypeRegistry.forEach((value, key) => { | |||
customRegistry.push([`/${key}`, value]); | |||
}); | |||
regenRegistry.forEach(([key, value]) => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
deleting this. As @blushi pointed out, the messageTypeRegistry
already registers all the custom regen msgs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
Closes: #60