pluginfw: Always include the function name in hook_fn_name

Plugin authors are allowed to omit the function name in the `ep.json`
parts definition. For example:

```
{
  "parts": [
    {
      "name": "ep_example",
      "hooks": {
        "authenticate": "ep_example",
        "authFailure": "ep_example"
      }
    }
  ]
}
```

If omitted, the function name is assumed to be the same as the hook
name. Before this change, `hook_fn_name` for the example hooks would
both be `/opt/etherpad-lite/node_modules/ep_example`. Now they are
suffixed with `:authenticate` and `:authFailure`. This improves
logging, and it makes it possible to use `hook_fn_name` to uniquely
identify a particular hook function.
This commit is contained in:
Richard Hansen 2020-09-05 17:00:26 -04:00 committed by John McLear
parent 6f3e7d14f6
commit 442fe1e86f
2 changed files with 7 additions and 3 deletions

View file

@ -39,7 +39,7 @@ function extractHooks(parts, hook_set_name, normalizer) {
* a dependency of another plugin! Bah, pesky little details of
* npm... */
if (normalizer) {
hook_fn_name = normalizer(part, hook_fn_name);
hook_fn_name = normalizer(part, hook_fn_name, hook_name);
}
try {