Problem/Motivation
The module provides multiple hooks, however none are documented in the content_lock.api.php file.
On a side note, I'm aware that there's a content_lock_entity_lockable hook, however it doesn't provide a way for third party modules with custom operations to alter the behaviour of the lock (e.g. in order to opt out).
Is this an intentional design decision?
Steps to reproduce
N/A
Proposed resolution
Create the content_lock_entity_lockable.api.php file with documentation for the appropriate hooks.
Remaining tasks
Provide a patch and commit.
Issue fork content_lock-3209982
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
smustgrave commentedSeems to still be relevant.
Comment #3
smustgrave commentedComment #4
smustgrave commentedComment #6
smustgrave commentedFull disclosure I'm not good at writing .api's but I gave it a shot. Hopefully a maintainer can fill in the gaps.
Comment #7
smustgrave commentedThis needs work but want to get feedback about what the api's are suppose to do
Comment #10
alexpott