fix issue in plugincontroller when loading plugins without info

allow admin components to skip being shown in the admin menu

This is related to #4249. At least the farmer plugin provides a top
level admin component and several sub components which are loaded fro

allow admin components to skip being shown in the admin menu

This is related to #4249. At least the farmer plugin provides a top
level admin component and several sub components which are loaded from
the top component. For this use case it makes sense to be able to hide
components from the admin interface. Default remains to show all.

show more ...

fix listing of plugin components

Plugins may have one main component of a type or they might have
multiple of the same type in a subdirectory.

Sometimes they may have both. This is often the case f

fix listing of plugin components

Plugins may have one main component of a type or they might have
multiple of the same type in a subdirectory.

Sometimes they may have both. This is often the case for organically
grown plugin, commonly with helper classes where a helper.php exists
first only to be extended by helper/*.php files later.

This patch fixes the listing of plugin(components) by type in the plugin
controller.

It also adjusts bin/plugin.php to handle plugin CLI components.

show more ...

sprintf expects ...args instead of an array. fixes #4193

Fix false errors when calling getInfo() from some plugins

API: code style fixes

Reworked API definition

This cleans up the API:

* no more compatibility with obsolete wiki API
* no more difference between wiki.* and dokuwiki.* calls -> core.*
* use of optional parameters avoids

Reworked API definition

This cleans up the API:

* no more compatibility with obsolete wiki API
* no more difference between wiki.* and dokuwiki.* calls -> core.*
* use of optional parameters avoids double definitions
* use Response objects for complex results
* always use named primitives as input
* major cleanup of docblock descriptions

show more ...

Fix first set of API tests

First go at refactoring the API mechanisms

This introduces an ApiCall class that wraps around the actual method
that produces the result. This replaces various loose array structures
that provided t

First go at refactoring the API mechanisms

This introduces an ApiCall class that wraps around the actual method
that produces the result. This replaces various loose array structures
that provided the meta information before.

The ApiCall streamlines the aggregation of meta information between core
and plugin methods. Now all data is produced by Reflection based
introspection. Certain aspects can be overridden if needed. See
ApiCore::getRemoteInfo() for examples

This change removes the _getMethods() method from remote plugins and
introduces a getMethods() method. The two are NOT compatible as the
latter now returns a list of ApiCalls. However when looking at the
existing plugins, it seems that _getMethods() was nearly 100% obsolete
with the Reflection based default implementation. So most plugins will
not be affected at all. Some might now export one or two more methods
than before because of poor visibility settings (eg. not declaring
private/protected methods as such).

This change removes the RPC_CALL_ADD hook. Only a single plugin ever
implemented it. I'm not sure what this hook was supposed to do anyway.
Being able to declare arbitrarily named API endpoints seems wrong to me
anyway.

The new ApiCall now also supports passing named instead of positional
parameters. This will open up a new opportunity to get a proper openapi
spec running.

Next step is fixing the tests.

show more ...

Automatically register composer autoloaders for plugins

The plugin controller will now automatically require vendor/autoload.php
for every plugin that has it.

ensure plugin.info.txt data is complete. fixes #4033

Conform to new coding style

Fix long line

Logic fix

Use str_starts_with/str_ends_with

�� Rector and PHPCS fixes

fix syntax plugin loading

It turns out our Syntax plugins never implemented the PluginInterface
(though they did use the PluginTrait). With our stricter type checking
in the plugin loader, these plu

fix syntax plugin loading

It turns out our Syntax plugins never implemented the PluginInterface
(though they did use the PluginTrait). With our stricter type checking
in the plugin loader, these plugins did not longer load.

show more ...

code style: line breaks

code style: static visibility

coding style: control flow whitespaces

recover comments in list

coding style: function call spacing

coding style: PSR12.Classes.ClassInstantiation.MissingParentheses

address issues mention in PR#4045

codestyle adjustments: EOF new lines