added user ability to add new tasks#12
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
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.
This pull request adds the ability for users to create new schema challenges through the frontend and backend. The main changes include a new "Create Challenge" page in the frontend, updates to the backend API to support challenge creation, and security adjustments to require authentication for challenge creation.
Frontend: New Challenge Creation UI
CreateChallengePage, which provides a form for users to input challenge details, schemas, test cases, and code templates. The form supports adding/removing multiple schemas and test cases, and submits the data to the backend.App.jsxto include the new/challenges/newroute and renderCreateChallengePagefor it. [1] [2]Backend: Challenge Creation API
/api/challengesinChallengeControllerto accept challenge creation requests, parse schemas and test cases, and persist the new challenge in the database. [1] [2]Security: API Access Control
/api/challenges, while still allowing unauthenticated GET requests. [1] [2]Development Environment