-
Notifications
You must be signed in to change notification settings - Fork 107
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
Shapella upgrade #786
Shapella upgrade #786
Conversation
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 great so far! 👏
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 took a deeper look at this and I think the current approach to versioning adds a lot of duplicated code.
Is there a way we can use generics to mitigate this problem?
@claravanstaden After some sync with Vincent offline, upgrade from Bellatrix is not nessessary for us and the previous implementation with versioning support is somewhat incomplete. To make things simple I change scope of this PR focus on Capella support only. |
Hey @yrong! That sounds good, I think keeping it simple is the correct way to go. However, even if we don't do the versioning now we still need to remember that it will be necessary for future prod cases when a hardfork is released. |
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 much better 🙌
Just need to remove the unnecessary Capella
from some struct names, please.
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.
🚢
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 great @yrong! 🥳
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.
Good to go! 🚀
No description provided.