fsa-grads-project/competition-site

Data structures and algorithms competition site

competition-site's Issues

Execute Bug Fix

Bug fix for executing code/problem in docker and retrieve results and consoles

• changing order of executable code (problem then code vs code then problem)
• remove calling runSubmission from problem and move to end of code
• comment out the runSubmission return from the consoleScript to prevent error

Create 'No Current Problem' Component

New Login Modal

Login modal should follow new redesign styling/format

Encrypt email addresses and add decryption functionality for future

Use crypto (node tool) to encrypt the emails for storage and build decrypt functionalities

Responsive Leaderboard

Two Styles:

Mobile: Similar style to the original layout where clicking on a user shows details, clicking on them again or anywhere else closes the details

Desktop: Shows full table with all details, sortable by total score/time score/space score

Re-Open Solved Problem

Once a solution for displaying a completed solution code is determined, create a button to re-open a solved problem

• Create button under the displayed solution code
  o onClick should open a modal stating something like 'reopening will affect your time to solve score. Are you sure you want to continue?' Yes or No
• create an asyncThunk to update the solution in the backend
• create a backend route to handle the updating of the solution (remove completeDateTime)
  o route should return the updated solution

Adding a user

When a new user is added it is currently done through the auth slice of the store and the new user is not added to the user slice. An update needs to be made so that the user is added to the state. Potentially this could just be an additional call to the fetchUsers thunk.

Bug Fixes

• Executing code: missing filepath variable in executeCode.js file
• Initial Code update: initial code in editor does not update when going from previous problem to current problem
• Incorrect os determination (ie need to swap intel and apple setup)
• Leaderboard resizing fix
• Minor leaderboard component cleanup

Navigation after logout

Currently after logout the user is redirected back to the landing page. This needs to be modified so that if they are on the current issue page they are redirected back to the landing page on logout, but if they are on any other page they should not be redirected on logout.

If no 'current' problem, website crashes

Tab Styling

Clean up tab styling

Create routes to save user code in backend

• Add 'blurb' to Problem model to only show a small portion of the problem statement
• create softVerifyUser which doesn't require the user to be logged in but if they aren't the route is still accessed
• Edit getCurrentProblem route to only return current problem AND determine if returned item is the full problem or just blurb based on if user is logged in
• Edit problem component to only show code section IF user is logged in
• create route to save user code in db onEvaluate
• update user code in db for problem and enter a 'submitted' date to close

Oauth Consolidation

Check to see if we can capture email from LinkedIn

Error handling for login

Errors are placed in the store by the thunk for logging in. If a login fails as an example due to an incorrect password, the error will carryover and display on the sign up page. Need to determine a method for updating the state so that the error is cleared when navigating away from the login page.

Evaluate Loading Spinner

Add a spinner for the evaluate button to indicate to the user when it is loading and when it's complete

Add OAuth Options

Add Github and Linkedin as Oauth options

Update past issues component

Update past issues component:

1. Set up the component to use actual past issues and not faker data

Complete login modals

Oauth issue w/ Google + Github using Firefox Browser

When trying to sign in to Google / Github using Oauth, I get the following errors:

It works when I use Chrome or Safari. So far, I've tried shutting down any ad blockers or plug-ins that might cause an issue. Also, cleared my cache to no avail.