-
-
Notifications
You must be signed in to change notification settings - Fork 297
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
V3 to V4 migration guide? #623
Comments
We're glad you find this project helpful. We'll try to address this issue ASAP. You can vist https://solothought.com to know recent features. Don't forget to star this repo. |
Hi @tylerblox , |
I'll try and play around with that a bit, adding that attribute to the config object didn't solve the problem by itself, but I'll see if I've missed something. After checking on the XmlParser object created, there is no method on it called "getTraversalObject" even after adding the attribute |
@tylerblox Sorry for the confusion what I meant to say is that "getTraversalObject" has been removed. Instead set preserve order to true to get intermediate object. |
I see what you mean thank you, I also have a diff of the objects returned in both cases, so I am planning on making the migrations soon. I appreciate the responses greatly. |
Description
Input
I'm wondering if there is any support for the methods from version 3 as I begin a migration to LTS version of fast-xml-parser
I use
provider.getTraversalObj()
in my project to extract the children nodes, and metatdata from xml files. Is there a solution where I can continue to use getTraversalObject to get the intermediate object, or alternatively, is there a guide for migrating away from using it?Thank you in advance for the help/advice.
Code
Output
In V4, the getTraversalObj function has been removed
Bookmark this repository for further updates. Visit SoloThought to know about recent features.
The text was updated successfully, but these errors were encountered: