Add User-Defined After-Init Hook #27
Merged
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
This feature adds the capability of defining a user-specific after-init hook, which gets executed by the init system after a project has been initialized. It works analogously to the after-init hook of an addon, but is completely independent of it. This means that no addon has to be loaded at all for a user-specific hook to take effect. However, when both an addon after-init hook as well as a user-defined after-init hook is available, the hook from the addon is first executed and then the user-defined hook. A user-defined after-init hook must be declared by the project.properties configuration file of the user. It must be declared by the property with key 'sys.user.hook.afterinit'. The property value must be a relative path to the hook script file. The path is relative to the user's home directory.
Closed
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.
Adds the capability of defining a user-specific after-init hook.
The declared script hook gets executed by the init system after a project has been initialized. It works analogously to the after-init hook of an addon, but is completely independent of it. This means that no addon has to be loaded at all for a user-specific hook to take effect. However, when both an addon after-init hook as well as a user-defined after-init hook is available, the hook from the addon is first executed and then the user-defined hook.
A user-defined after-init hook must be declared by the project.properties configuration file of the user. It must be declared by the property with key 'sys.user.hook.afterinit'. The property value must be a relative path to the hook script file. The path is relative to the user's home directory.