7de5ac55 | 06-Jan-2024 |
Andreas Gohr <andi@splitbrain.org> |
Another argument parsing fix for ApiCall
When using named parameters, you can expect to be able to leave out any optional parameter and have it take it's default, even when you specify another "late
Another argument parsing fix for ApiCall
When using named parameters, you can expect to be able to leave out any optional parameter and have it take it's default, even when you specify another "later" parameter. Luckily we already know all the defaults from reflection anyway.
show more ...
|
5b379b50 | 01-Dec-2023 |
Andreas Gohr <andi@splitbrain.org> |
fix ApiCall test on PHP7.4
Since PHP7.4 has no primitive type hints and PHP native methods have no accessible docblocks, we can not use a native function for testing (types always come back as strin
fix ApiCall test on PHP7.4
Since PHP7.4 has no primitive type hints and PHP native methods have no accessible docblocks, we can not use a native function for testing (types always come back as string).
show more ...
|
42e66c7a | 30-Nov-2023 |
Andreas Gohr <andi@splitbrain.org> |
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 ...
|