Skip to content

Conversation

@jaapio
Copy link
Member

@jaapio jaapio commented Jan 3, 2020

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.

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.
@jaapio jaapio requested a review from mvriel January 3, 2020 12:36
Copy link
Member

@mvriel mvriel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed; with a couple of suggestions for possible improvements

@jaapio jaapio force-pushed the fix/invalid-tag-usage-fix branch from 135db42 to bb629f6 Compare January 12, 2020 12:19
@jaapio jaapio merged commit f256f0b into master Jan 12, 2020
@jaapio jaapio deleted the fix/invalid-tag-usage-fix branch January 12, 2020 12:26
@jaapio
Copy link
Member Author

jaapio commented Jan 12, 2020

Thanks for the review. Updated the code and merged it to master.
We might want to merge this to v4? however, this is a breaking change?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants