Auto-Grouping functionality #8
Open
Conversation
This file contains 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.
Hello,
first of all I would like to thank you for developing this plugin. In our project we wanted to implement something similar to the adapt-contents plugin. Since the adapt-contents plugin was not compatible with the current Adapt framework version, we found this repository, but we were missing an auto-grouping functionality that reflects the course structure. This pull request is intended to solve this problem. The auto-grouping functionality is added as an option in the course.json configuration ("_enabled": true; see example.json), leaving the other options untouched. The "_maxLevel" defines how deep the nested autoGroups should be / where the cutoff for contentObjects should be: 0 => menu/page; 1 => article; 2 => block; 3 => component.
The following graphic is intended to demonstrate the functionality symbolically; the CSS used to visually distinguish the contentObjects from the groups is not part of the pull request.