You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What would be nicer is that when the value is called with __toString() which triggers that reaction of printing a formatted
[
"sub_value" => 'stripes'
]
or if the values is just called by the magic __get it should return the value as a php array type, instead of assuming that it may be calling another dynamically generated value.
The text was updated successfully, but these errors were encountered:
Actually this was fixed by #15 ... the toString returns the JSON array, can make it be JSON_PRETTY 😝 lol, but still this >
or if the values is just called by the magic __get it should return the value as a php array type, instead of assuming that it may be calling another dynamically generated value.
When a object is assigned to a value e.g.:
What would be nicer is that when the value is called with
__toString()
which triggers that reaction of printing a formattedor if the values is just called by the magic
__get
it should return the value as a php array type, instead of assuming that it may be calling another dynamically generated value.The text was updated successfully, but these errors were encountered: