ryedin

  • Joined on
ryedin commented on pull request Leonidas-from-XIV/node-xml2js#190
@ryedin

No worries man. Thanks for taking the time to do the merge and to maintain this project in general! Good luck on the thesis!

ryedin commented on pull request Leonidas-from-XIV/node-xml2js#190
@ryedin

sooo... hey man, not trying to be a pest, but it's been a couple weeks. I already have a project in production now depending on this patch (pointin…

ryedin commented on pull request Leonidas-from-XIV/node-xml2js#190
@ryedin

poke. I updated to fix merge conflict in package.json (contrib section) + added support for preserving the ordering of text nodes with markup inside.

@ryedin
ryedin commented on pull request Leonidas-from-XIV/node-xml2js#190
@ryedin

I just modified the PR with a commit that will retain the behavior of the named (unordered) fields (removes the #name property and collapses text-o…

@ryedin
  • @ryedin c98467a
    preserve prior behavior of named (unordered) properties with regards …
@ryedin

OK, so, the above PR provides us with what I view is a viable workaround for this issue. In this configuration the parser behaves like normal (stil…

ryedin commented on pull request Leonidas-from-XIV/node-xml2js#190
@ryedin

Let me know if there are any changes needed. I think it slightly modifies behavior of text nodes. Since all nodes now retain the #name property (fo…

@ryedin
@ryedin
added configuration to allow preservation of child node ordering
1 commit with 70 additions and 31 deletions
@ryedin

OK, I'll make a fork and take a look at the code to see if I can come up with something. No promises of course :)

@ryedin

Any update on this issue? This is a very common issue in a lot of XML docs. I would think the solution here could be as simple as changing the obje…

ryedin commented on issue shouldjs/should.js#57
@ryedin

Heh, yeah ok, now that I think of it more I see where my brain was failing me :)

ryedin commented on issue shouldjs/should.js#57
@ryedin

OK, so this may be a non-issue / misunderstanding. should.not.exist("123") works, but "123".should.not.exist does not. Leaving it open in case the "…

@ryedin
"123".should.not.exist is not failing as expected
@ryedin
package.json version discrepancy (github vs npm)
ryedin commented on issue noflo/noflo-ui#455
@ryedin

@ensonic before your PR here #457, component loading never worked for me against my nodejs runtime. Now it does, but I have to refresh the page aft…

ryedin opened issue noflo/noflo-ui#459
@ryedin
component loading from nodejs-runtime hangs on first load
ryedin commented on issue noflo/noflo-ui#455
@ryedin

So this doesn't 100% resolve the issue on my end. On first attempt at loading a subgraph I still get the orange 'Loading...' header bar that hangs.…

ryedin opened issue noflo/noflo-ui#456
@ryedin
subgraph component port ordering
ryedin commented on issue noflo/noflo-ui#452
@ryedin

My apologies again for the issue duplication, will try to do a better job searching existing issues going forward...

ryedin commented on issue noflo/noflo-ui#451
@ryedin

@forresto ah, my bad for duplicating issues then (I didn't make the connection) what about the graph auto zooming in to the max setting making it a…

ryedin opened issue noflo/noflo-ui#452
@ryedin
dropping subgraph onto itself explodes the universe
ryedin commented on issue noflo/noflo-ui#451
@ryedin

That would also explain how the undo button did not appear to do anything when #449 happened

ryedin commented on issue noflo/noflo-ui#451
@ryedin

This might be what actually happened to me here: #449 I'm willing to bet this is it. Somehow the mini-map and zoom setting of the graph area got in…

ryedin opened issue noflo/noflo-ui#451
@ryedin
mini-map incorrect and wonky after creating new graph
ryedin commented on issue noflo/noflo-ui#289
@ryedin

examples !== tutorials, guys. A tutorial starts with nothing, and slowly adds concepts that build up as you go, bit by bit, with good explanations…

ryedin commented on issue noflo/noflo-ui#397
@ryedin

@bergie github is not necessarily the end-all here. For private projects it would be much nicer to point to a local git repo. While the generic ess…