Release 0.5.2 #54
Closed
Release 0.5.2 #54
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
Overwrote methods for extracting relative file paths, so that tey can be used on other repo types, not only assignments. to fix: all files from source are still copied to the release repo ref: #8
to do: we have to think about how we want to release assignment (assignment-status.tsx), should it be left as it is -> always pushing all files from source directory or like pushing files from source where we can choose files to push (other possibility is to take those files that were selected to push and to push them, if none were previously selected, meaning there were no pushes, than push everything from source) ref: #8
…it file list. ref: #8
…state-of-submissions Add submission restore functionality
Better error page
This also required changing FilesList definition in edit submission view, where the same error was caused. Ref: #41
select files during commit process
…te-submission Ref: #41
feat: updated file pattern
… Omitted unnecessary Typography element in edit-submission.tsx. #27
Added react Dev Tools to Dev dependencise for debugging purposes, will be deleted from components later. To Do: FileLists send requests for each file that is shown, which shouldnt be the case -> to fix.
…check file remote status of each file in the directory.
Manually merged release-0.4.1 branch and 27-new-caching-solution. Closes #27
…ft hand side, it was stuck on one initially opened assignment when navigating through assignments.
…ace in useEffect.
…arked as "extra file". This was because file query was initially setting files to an empty array and not waiting for them to be completely loaded.
Fixed file browser model API calls
…number instead of just the number to make it more clear what is returned.
47 unsubmitting assignments
This reverts commit 62e8009.
…ern for assign generation
…extension into release-0.5.0
…ready been generated If number of submissions was limited, and the user happens to have used all submission credits and to have deleted all submissions and there is only one left we show message, that if that submission gets deleted, there is no next chance and tey won't be able to submit again, but will be graded with 0 points. #53
…-allowed Merge #53 "Submission should not be able to be deleted if feedback was already generated" into release 0.5.0
…er_config.py is removed from release)
…ubmissions are displayed instead of just the current users submissions
…signments queries, fixed that. Added "await" to all query invalidations.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
No description provided.