-
Notifications
You must be signed in to change notification settings - Fork 217
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
chore: normalize chain info #10109
base: master
Are you sure you want to change the base?
chore: normalize chain info #10109
Conversation
- counterParty -> counterparty - prefer camelCase to snake_case for JS conventions - prefer flattened counterparty fields (counterpartyConnectionId)
Deploying agoric-sdk with Cloudflare Pages
|
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.
For asset info, I think consistency with the chain registry is more important than JS norms.
denom_units: [ | ||
denomUnits: [ |
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.
This was sourced from the chain registry. I don't think it's cost-effective to be different.
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.
never mind.
looks like we're already tweaking such names.
portId: channelFrom.port_id,
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.
let's definitely fix counterParty ASAP
_incidental_ ## Description We don't have a good design yet for the schema of Orchestration chain info in agoricNames, - #10109 It's not necessary for upgrade-17 so save it for another proposal. ### Security Considerations none ### Scaling Considerations none ### Documentation Considerations SDK still registers the info so the development experience doesn't differ. ### Testing Considerations Shouldn't break any existing tests. ### Upgrade Considerations Not yet deployed. Should be part of u17-rc1.
_incidental_ ## Description We don't have a good design yet for the schema of Orchestration chain info in agoricNames, - #10109 It's not necessary for upgrade-17 so save it for another proposal. ### Security Considerations none ### Scaling Considerations none ### Documentation Considerations SDK still registers the info so the development experience doesn't differ. ### Testing Considerations Shouldn't break any existing tests. ### Upgrade Considerations Not yet deployed. Should be part of u17-rc1.
closes: #9807
Description
Normalizes chain info for agoricNames:
Security Considerations
n/a
Scaling Considerations
n/a
Documentation Considerations
n/a
Testing Considerations
Existing tests updated as this is just a rename.
Upgrade Considerations
Will require a proposal to update this data if this doesn't land in u17