-
Notifications
You must be signed in to change notification settings - Fork 0
Fix TypeScript compilation errors from Zod-inferred DriverInterface type mismatch #147
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||
|---|---|---|---|---|
|
|
@@ -19,7 +19,8 @@ import { | |||
| HookContext, | ||||
| ActionHandler, | ||||
| ActionContext, | ||||
| LoaderPlugin | ||||
| LoaderPlugin, | ||||
|
||||
| LoaderPlugin, |
Copilot
AI
Jan 21, 2026
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.
Using type assertion 'as any' bypasses TypeScript's type checking and defeats the purpose of having strong type safety. While this is documented as a workaround for structural compatibility with spec's DriverInterface, it eliminates compile-time verification that our Driver interface is actually compatible with DriverInterface. Consider either: (1) creating a proper type adapter/wrapper function that ensures compatibility at compile time, or (2) contributing to @objectstack/spec to export a non-Zod-inferred Driver type that can be structurally matched.
Copilot
AI
Jan 21, 2026
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.
Using type assertion 'as any' bypasses TypeScript's type checking and defeats the purpose of having strong type safety. While this is documented as a workaround for structural compatibility with spec's DriverInterface, it eliminates compile-time verification that our Driver interface is actually compatible with DriverInterface. Consider either: (1) creating a proper type adapter/wrapper function that ensures compatibility at compile time, or (2) contributing to @objectstack/spec to export a non-Zod-inferred Driver type that can be structurally matched.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
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.
Incomplete or malformed JSDoc comment. Line 513 contains an empty JSDoc opener that should be removed, as line 515 starts the actual documentation for the introspectSchema method.