Implement Participant page using DataTables. Fix circular import in d… #1484
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.
…ev environment.
Description
Implement the Participants page using the DataTables plugin, like in the All Results page. Has a lot better performance on large courses as there are no menus for adding user tags on each row, but instead a simple button which opens a dialog. Also the user tags are not transferred as HTML snippets from the backend, but instead a list of slugs and ids. Buttons to add/remove student tags for selected students are added as well.
This PR also contains a fix for a frequently appearing circular import issue in the development environment.
It also contains a change for the base.html, as browsers were complaining about the preloaded translation files. They are now marked as prefetch instead of preload.
Testing
Only manually tested to get this into production quickly. There are some inline CSS styles that need to be moved into a more proper place, but this can be done in the next minor update.
Remember to add or update unit tests for new features and changes.
What type of test did you run?
[ADD A DESCRIPTION ABOUT WHAT YOU TESTED MANUALLY]
Did you test the changes in
Think of what is affected by these changes and could become broken
Translation
Programming style
Have you updated the README or other relevant documentation?
Is it Done?
Clean up your git commit history before submitting the pull request!