Skip to content
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

Prompting Testing #61

Merged
merged 11 commits into from
Apr 10, 2024
Merged

Prompting Testing #61

merged 11 commits into from
Apr 10, 2024

Conversation

AidanScharnikow
Copy link

@AidanScharnikow AidanScharnikow commented Apr 6, 2024

Please review the created SQL statements on the database. I will be continuing to fine-tune but want some feedback on how the SQL statements are performing. Thank you. I also added some error checking. This ensures that if a SQL statement is not successfully returned or the SQL statement flags SQL injection, direct the user to re-prompt page.

Copy link

@alishahidd alishahidd left a comment

Choose a reason for hiding this comment

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

Looks good.

@alishahidd alishahidd merged commit ae66900 into main Apr 10, 2024
3 checks passed
Copy link

@zyij99 zyij99 left a comment

Choose a reason for hiding this comment

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

fails to start backend with these changes. Dont remove the venv file from gitignore & personally, i think yarn.lock should be kept in the file despite creating merge conflicts since it's usage is similar to package-lock.json and package.json

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants