fix: avoid retriggering the CONFIG_LOADED action multiple times.#186
Merged
Conversation
DonatoBD
approved these changes
May 28, 2026
The get_init_tasks function is called a few times inside the Jinja2 templates. The function used internal Tutor modules to load the user configuration, this caused the `CONFIG_LOADED` action to trigger hooks multiple times. Instead of manually load the Tutor configuration using Tutor's internal functions we now rely on the very same `CONFIG_LOADED` action to register a hook that will store the value of the configuration in a global variable.
MoisesGSalas
force-pushed
the
mgs/fix-config-load-retrigger
branch
from
2cca1de to
11c7710
Compare
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
2 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.
The get_init_tasks function is called a few times inside the Jinja2 templates. The function used internal Tutor modules to load the user configuration, this caused the
CONFIG_LOADEDaction to trigger hooks multiple times.Instead of manually load the Tutor configuration using Tutor's internal functions we now rely on the very same
CONFIG_LOADEDaction to register a hook that will store the value of the configuration in a global variable.