Feat/sql history#23
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 introduces a new feature for SQL challenges: users can now view their submission history via an API endpoint and a modal in the UI. It also adds security improvements to challenge previewing and enhances the user experience by preventing copying or selecting challenge descriptions. Additionally, several static asset files are updated, likely due to a rebuild after code changes.
SQL Challenge Submission History Feature:
/api/v1/challenges/<int:challenge_id>/sql-submissions) to fetch a user's submission history for SQL challenges, with authentication required and proper error handling.showSubmissionHistory) to display submission history in the challenge UI, including formatted dates and status indicators. [1] [2]Security and Access Control Improvements:
User Experience Enhancements:
Static Asset Updates:
challenges.cd891a5f.js,clipboard.6907d1dc.js,index.86a4c4d6.js) to reflect dependency changes and new code for the above features. [1] [2] [3]Miscellaneous:
.github/workflows/lint.yml, possibly for testing or to disable CI linting temporarily.