Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Context of warnings is empty in JSON result #26

Merged
merged 3 commits into from
Dec 5, 2016
Merged

Context of warnings is empty in JSON result #26

merged 3 commits into from
Dec 5, 2016

Conversation

cawolf
Copy link
Contributor

@cawolf cawolf commented Jul 24, 2016

Hi, first of all, thanks for this great project.

When running the analyzer against our company source code, I noticed that the console logging differs from the JSON result file regarding the contexts of the warnings. While the file paths are being correctly printed in the console, the JSON file contains only empty arrays.

I traced it down to the inability of json_encode to call SplFileInfo::__toString (compare with http://stackoverflow.com/questions/401908/php-tostring-and-json-encode-not-playing-well-together ) and added a little wrapper class to overcome this issue.

I appreciate any feedback and hope you will merge this to your codebase,
best regards,
Christian A. Wolf

@cawolf
Copy link
Contributor Author

cawolf commented Nov 24, 2016

Hey @mamuz, do you need anything else from me to have a look at this PR?
Best regards,
Christian

@mamuz mamuz merged commit 4296c35 into mamuz:master Dec 5, 2016
@mamuz
Copy link
Owner

mamuz commented Dec 5, 2016

Hi @cawolf, thanks for the PR and sorry for long waiting. Its merged, next days i will create a new release.

@cawolf cawolf deleted the fix-context-warnings-empty branch December 18, 2016 13:02
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.

2 participants