When invalid tags are processed a null was returned causing all kind
of issues in the normal behavior of this libary. As a solution a generic tag
could be created. But that would just drop the error information in.
Therefore a new tag was introduced, `invalidTag` the tag is just like the
generic tag but does contain the error triggered during the creation of the
tag. Which might help applications like phpdocumentor to display validation issues.
In this change, I have introduced a miniature automaton-light to parse
the type from the @return body. This will prevent issues with people
using generics and other unsupported forms of types.
This change does _not_ allow for the use of Generics or similar; the
TypeResolver will still fail to resolve this type. This will remove a
breaking issue in consuming applications where a runtime exception used
to be thrown.
Please note that this change is only for @return; other tags still need
to be done. This will resolve issue #186
When a tag has an invalid component to it it would cause a whole file to fail
to parse. Instead we should consider invalid tags a nuisance but not worth
breaking the whole parsing over.
In this change I have added a try..catch that will prevent invalid tags from
breaking the whole parsing process.
* composer: put require- together
* add phpstan
* add phpstan to travis
* phpstan fixes
* phpstan fixes
* phpstan fixes
* drop null defaults since every property is null by default
* DescriptionFactory: fix parse nullable type
* travis: add phpstan max
* travis: fix phpstan config
Without this sort the order of argument name and type matter. But
we accually don't care about the order. Only name and type are allowed
but the order doesn't matter.
Jaapio
Mike van Riel
Corey Taylor
Michael Knappe
Chuck Burgess
TomasVotruba
Gabriel Caruso
Tomáš Votruba
Bozhidar Hristov