-
Notifications
You must be signed in to change notification settings - Fork 188
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
fix(katana): separate deprecated declared class #2903
Conversation
WalkthroughOhayo, sensei! This pull request focuses on refining the handling of deprecated declared classes across multiple components of the Katana project. The changes introduce a more nuanced approach to managing class declarations, specifically distinguishing between active and deprecated classes. The modifications span several key files in the executor, primitives, RPC types, and storage provider modules, implementing a consistent strategy for tracking legacy classes using Changes
Possibly related PRs
Suggested reviewers
📜 Recent review detailsConfiguration used: .coderabbit.yaml 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
Documentation and Community
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2903 +/- ##
==========================================
+ Coverage 55.84% 56.05% +0.20%
==========================================
Files 449 449
Lines 57730 57861 +131
==========================================
+ Hits 32242 32434 +192
+ Misses 25488 25427 -61 ☔ View full report in Codecov by Sentry. |
Currently, we're including both legacy and non-legacy into the same map in the
StateUpdates
struct, while instead the legacy should be put into a different map iedeprecated_declared_classes
.Summary by CodeRabbit
Release Notes
New Features
Bug Fixes
Refactor