check feed validity at w3c validator

Update rector and the used class namespace

Seems like the class alias for Rector\Core is removed in 19.2 This
should fix the rector runs on github.

Feed creation refactoring

This breaks up the humongous functions from feed.php into multiple
classes. To keep compatibility with existing Plugin events, the basic
principle of how the feed is assemb

Feed creation refactoring

This breaks up the humongous functions from feed.php into multiple
classes. To keep compatibility with existing Plugin events, the basic
principle of how the feed is assembled has not been changed:

* depending on the given mode and other options lose arrays of items are
gathered
* these items are then converted (again based on the various options)
into proper FeedItems
* the FeedItems are then added to the Feed

The conversion from loosely typed item data to something more structured
is now done by the FeedItemProcessor classes. Some very basic tests have
been added. It does not cover erverything but covers more than before
(which was nothing).

Manual testing before merging this is highly recommended. I am not
confident that I ported over everything correctly.

No new features have been added, but especially media support could and
should be improved in the future.

show more ...

fall back to empty (root) dir for base dir detection

When a basedir could not be detected, the default previously was '.'
resulting in a valid but weird URL (http://example.com/./doku.php). We
now d

fall back to empty (root) dir for base dir detection

When a basedir could not be detected, the default previously was '.'
resulting in a valid but weird URL (http://example.com/./doku.php). We
now default to an empty dir, resulting in a more sensible URL of
http://example.com/doku.php

This should not matter in real web server setups but will be in effect
while testing.

show more ...

add (failing) compability test for AES encryption

tune parallel tasks in rector

The default options for running paralell rector tasks changed in 0.19
resulting in failures on github runners.

See also https://github.com/rectorphp/rector/issues/8396

update rector

API added simple JSONRPC tests

fix XMLRPC server tests

We test against the MockAPICore now since the tests are meant to ensure
the general functionality of accepting XML and correctly calling
APICalls works, not that the API retu

fix XMLRPC server tests

We test against the MockAPICore now since the tests are meant to ensure
the general functionality of accepting XML and correctly calling
APICalls works, not that the API returns the right things (this is
tested in the ApiCore tests).
Since we no longer use dates but always integers, we no longer need to
handle that.

show more ...

Fix Api Tests

fix ApiCoreAclCheckTest

This is mostly syntactic fix. I did not check how sensible these tests
are and did not switch from positional to named arguments

API: move user related tests to usermanager plugin

API: ApiCore tests fixed and extended

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 ...

Clean up APICall tests

No need to retest all the docblock parsing when that is tested elsewhere
already.

API: fix named parameter handling in APICall

We cannot set missing paramerers to null. We need to make sure they are
not set at all.

OpenAPI Generator. Better DocBlock parsing [WIP]

This introduces a new DocBlock parser to properly generate API
specifications. It also introduces the concept of Response classes to
better specify t

OpenAPI Generator. Better DocBlock parsing [WIP]

This introduces a new DocBlock parser to properly generate API
specifications. It also introduces the concept of Response classes to
better specify the response format.

This is still very much in progress.

show more ...

fix ApiCall test

fix type parsing for more complex types

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 ...

final set of API tests refactored

More adjusted API tests

another set of api tests

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 ...