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
The current parser is great. It would also be great to have a serializer/deserializer in the tone of json_encode/json_decode with options. If course this would only work consistently for a subset and would not be able to bring a full specs KDL doc into a PHP structure/object/arrays and then back without loosing/discarding data (e.g comments)
Since the logic/nodes etc (in my not too well versed in KDL opinion) could be seen as similar to an XML document serialization (with better typed data, etc), maybe some type of decorator type of processing (again going back to you can do that in PHP from XML to JSON) could work?
Just wondering if this is something others may want or the parse suffices the need. Thanks!
The text was updated successfully, but these errors were encountered:
I'd wait until the deserialised format has stabilised after there's full compliance with KDL 1.0 before writing any code to go back the other way - but some functionality to do that would be good and something I'd intend to add.
Likewise I'm interested in whether it's something people have an active need for.
What?
The current parser is great. It would also be great to have a serializer/deserializer in the tone of json_encode/json_decode with options. If course this would only work consistently for a subset and would not be able to bring a full specs KDL doc into a PHP structure/object/arrays and then back without loosing/discarding data (e.g comments)
Since the logic/nodes etc (in my not too well versed in KDL opinion) could be seen as similar to an XML document serialization (with better typed data, etc), maybe some type of decorator type of processing (again going back to you can do that in PHP from XML to JSON) could work?
Just wondering if this is something others may want or the parse suffices the need. Thanks!
The text was updated successfully, but these errors were encountered: