Repository navigation
refactor(database): migrate both workspaces to published SDKs - #17
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
1 participant
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.
Summary
Replace vendored shared, driver, and GTM packages with published npm SDKs in both main and release-v5.1, and use the Desktop SDK directly.
Keep application-owned HostConfig stores and a main quota-dialog adapter to preserve currency and subscription behavior; update imports, dependency lockfiles, transpilation, documentation, and regression tests.
Validation
Both workspace TypeScript checks, 15 HostConfig tests, four deployment compatibility tests, and the pre-commit gitleaks scan passed.
Production builds and browser interaction were not verified.
Sequence Diagram
sequenceDiagram participant App as Database app participant SDK as Published Desktop SDK participant Desktop as Sealos Desktop participant Store as App HostConfig store participant UI as Price and quota UI App->>SDK: Initialize and request HostConfig once SDK->>Desktop: Get host configuration alt Configuration available Desktop-->>Store: Currency and subscription settings else Legacy host or request failure SDK-->>Store: Apply compatible defaults end Store-->>UI: Render currency and subscription controls