Skip to content

Fix unescaped unicode encoding parameter #25

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

Closed
wants to merge 2 commits into from

Conversation

landrok
Copy link
Contributor

@landrok landrok commented Sep 13, 2016

3rd parameter for json_encode is a max depth limitation. JSON_UNESCAPED_UNICODE has an int value of 256 whereas the max depth value is 512 (so no matter this way). This patch restores the expected usage of UNESCAPED_UNICODE param which is to
encode multibyte Unicode characters literally.

3rd parameter for json_encode is a max depth limitation. JSON_UNESCAPED_UNICODE has an int value of 256 whereas the max depth value is 512 (so no matter this way). This patch restores the expected usage of UNESCAPED_UNICODE param which is to
encode multibyte Unicode characters literally.
L116 
```        } catch (Exception $e) { // can't be catched because CodeClimate\PHPMD\Exception does not exist```
Another way to fix this is:
```        } catch (\Exception $e) {```
@landrok
Copy link
Contributor Author

landrok commented Sep 13, 2016

Sorry, I did not want to pull this 2 patches into one. I'll close and reopen 2 separated pulls in a moment.

@landrok landrok closed this Sep 13, 2016
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.

1 participant