-
```
What steps will reproduce the problem?
1. trace( JSON.encode( ) );
What is the expected output? What do you see instead?
Like Date instance (see issue #2), there is no standard XML encoding syn…
-
```
What steps will reproduce the problem?
1. trace( JSON.encode( ) );
What is the expected output? What do you see instead?
Like Date instance (see issue #2), there is no standard XML encoding syn…
-
```
What steps will reproduce the problem?
1. trace( JSON.encode( ) );
What is the expected output? What do you see instead?
Like Date instance (see issue #2), there is no standard XML encoding syn…
-
```
What steps will reproduce the problem?
1. trace( JSON.encode( ) );
What is the expected output? What do you see instead?
Like Date instance (see issue #2), there is no standard XML encoding syn…
-
This would be useful to test if what I've written into `composer.json` is correct and whether the build actually works, before committing to my changes by pushing them into a public repository and sub…
-
First thanks for a useful library. It has cut JSON printing times substantially for my project.
I have come across some inconsistent behavior that seems to come from [line](https://github.com/h4l/j…
-
I've been using this extension for a while now and I've found it very useful. Thanks for sharing your work.
I'm now trying to add support to a different project in the same solution. The second pro…
-
```
What steps will reproduce the problem?
1. trace( JSON.encode( ) );
What is the expected output? What do you see instead?
Like Date instance (see issue #2), there is no standard XML encoding syn…
-
```
What steps will reproduce the problem?
1. trace( JSON.encode( ) );
What is the expected output? What do you see instead?
Like Date instance (see issue #2), there is no standard XML encoding syn…
-
```
What steps will reproduce the problem?
1. trace( JSON.encode( ) );
What is the expected output? What do you see instead?
Like Date instance (see issue #2), there is no standard XML encoding syn…