Skip to content

Generate prisma client #65

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.

Sign up for GitHub

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

Merged
vas3a merged 2 commits into from
Jan 26, 2026
Merged

Generate prisma client #65

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5d31d1f
Generate prisma client
vas3a Jan 23, 2026
1da01a9
match features for prisma client
vas3a Jan 23, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions packages/challenge-prisma-client/client.d.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
export * from "./index"
Copy link

@github-actions github-actions bot Jan 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[💡 style]
Consider adding a newline at the end of the file. While this is not a correctness issue, it is a common convention that can prevent potential issues with some tools and version control systems.

5 changes: 5 additions & 0 deletions packages/challenge-prisma-client/client.js
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@

/* !!! This is code generated by Prisma. Do not edit directly. !!!
/* eslint-disable */
// biome-ignore-all lint: generated file
module.exports = { ...require('.') }
Copy link

@github-actions github-actions bot Jan 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[⚠️ maintainability]
Using require('.') without specifying a specific file or module can lead to unexpected behavior if the directory structure changes. Consider explicitly requiring the intended module for better maintainability and clarity.

1 change: 1 addition & 0 deletions packages/challenge-prisma-client/default.d.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
export * from "./index"
Copy link

@github-actions github-actions bot Jan 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[💡 style]
Consider adding a newline at the end of the file to comply with POSIX standards and improve compatibility with various tools that expect a newline at the end of files.

5 changes: 5 additions & 0 deletions packages/challenge-prisma-client/default.js
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@

/* !!! This is code generated by Prisma. Do not edit directly. !!!
/* eslint-disable */
// biome-ignore-all lint: generated file
module.exports = { ...require('#main-entry-point') }
Copy link

@github-actions github-actions bot Jan 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[❗❗ correctness]
The use of require('#main-entry-point') with a spread operator assumes that the module exports an object. If #main-entry-point exports something other than an object (e.g., a function or a primitive), this will cause a runtime error. Consider adding validation or handling for non-object exports to prevent potential issues.

1 change: 1 addition & 0 deletions packages/challenge-prisma-client/edge.d.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
export * from "./default"
Copy link

@github-actions github-actions bot Jan 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[💡 style]
Consider adding a newline at the end of the file. While this is not a correctness issue, it is a common convention that can help avoid unnecessary diffs in version control systems when lines are added to the end of the file.

Loading
Loading