Challenge winners - make sure Prisma schema updated with new enum value #66
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
| challengeIds = options.challengeIds.slice(); | ||
| } else { | ||
| const rows = await reviewClient.$queryRaw` | ||
| SELECT DISTINCT "challengeId" AS id |
There was a problem hiding this comment.
[❗❗ security]
Using raw SQL queries with template literals can lead to SQL injection vulnerabilities. Consider using parameterized queries or Prisma's query builder methods to ensure safety.
|
|
||
| const rows = isMarathonMatch | ||
| ? await reviewClient.$queryRaw` | ||
| SELECT |
There was a problem hiding this comment.
[❗❗ security]
Using raw SQL queries with template literals can lead to SQL injection vulnerabilities. Consider using parameterized queries or Prisma's query builder methods to ensure safety.
| GROUP BY s.id, s."challengeId", s."memberId", s."submittedDate", s."createdAt" | ||
| ` | ||
| : await reviewClient.$queryRaw` | ||
| SELECT |
There was a problem hiding this comment.
[❗❗ security]
Using raw SQL queries with template literals can lead to SQL injection vulnerabilities. Consider using parameterized queries or Prisma's query builder methods to ensure safety.
| } | ||
|
|
||
| const rows = await reviewClient.$queryRaw` | ||
| SELECT id, "minScore", "minimumPassingScore" |
There was a problem hiding this comment.
[❗❗ security]
Using raw SQL queries with template literals can lead to SQL injection vulnerabilities. Consider using parameterized queries or Prisma's query builder methods to ensure safety.
| ); | ||
| } | ||
|
|
||
| main().catch((error) => { |
There was a problem hiding this comment.
[maintainability]
Consider adding more specific error handling or logging to provide better insights into what went wrong during execution.
No description provided.