-
Notifications
You must be signed in to change notification settings - Fork 42
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
Using quick-xml #68
Comments
I was planning to wait until specialisation was stable so that we can wrap our |
Any updates on this one? If you need any help, I can volunteer |
I've added this to V1.4 as a nice-to-have. I'm not sure if I'll have time to work on it or if @pr2502 has time to finish #78, and would be very happy to accept a PR switching to It doesn't look like A way forward would be to add Then, when specialization becomes stable, we can specialise for |
Thanks for this introduction. I'd like to work on this after I finish my current workload. It seems like I will have the time (most probably, but I cannot promise). |
I've wanted to look into a plist file I couldn't parse again, and before looking deeper into #52, I decided to look into the quick-xml topic again. #88 now contains an up-to-date port to quick-xml, mostly based on @pr2502's work, but with the remaining mentioned issues fixed up and it being rebased on master. The test suite now fully passes again, so if some people could try it out, that'd be great. |
Closed by #88. Thank you again @jcgruenhage for your work on this. |
I see in the 1.0 checklist that you'd like to use quick-xml for the XML part. Me too. What specifically would need to be done?
The text was updated successfully, but these errors were encountered: