update quicknode naming#14
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
Medium Risk
Wide-surface rename across multiple language bindings and published APIs; primary risk is breaking downstream imports/usages or missing an export/exception mapping in one language.
Overview
Standardizes public naming across all bindings by renaming the top-level client from
QuickNodeSdktoQuicknodeSdkand the base exception fromQuickNodeErrortoQuicknodeError(plus corresponding Ruby module/class renames).Updates all language wrappers/exports (Rust core type, Python PyO3 classes +
__init__exports/stubs, Node napi + JS/TS wrappers, Ruby magnus classes), along with docs, examples, and various docstrings to match the new casing and gem name (quicknode_sdk).Reviewed by Cursor Bugbot for commit 7796b1f. Bugbot is set up for automated code reviews on this repo. Configure here.