1/ wow, the Ruby Hash.from_xml() sucks feed it "<Foo>text</Foo>" and it gives { Foo => text } feed it <Foo a=b/> and it gives { Foo => { a => b } } Both good results. But combine those two XML features ...
-
Show this thread
-
2/ "<Foo a=b>text</Foo>" and it gives {Foo => text} what happened to the attribute value assignment a=>b ? Just disappeared! :frown:
3 replies 0 retweets 7 likesShow this thread -
3/ So, using the nokogiri gem elsewhere; will play with that for what I had THOUGHT was going to be a trivial bit of parsing sigh nothing's ever easy
2 replies 0 retweets 5 likesShow this thread -
ⓘ Dogs don't have thumbs Retweeted
4/ The problem I'm trying to solve by parsing XML is parsing XML. Not trying to be (too) snarky, but I am coding to a Very Baroque web interface by a Very Baroque Large Firm, and their web services speaks XML. >>> https://twitter.com/RedeemedCat/status/1283074012638179328 …
ⓘ Dogs don't have thumbs added,
This Tweet is unavailable.2 replies 0 retweets 6 likesShow this thread
5/ and I've already got my server which handles inbound SOAP / XML requests from LARGE FIRM working, and I'm composing XML responses, as I am required to so now in my mock / test harness / regression test client which pretends to be BIG FIRM I'm inspecting real XML return doc
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.