{"issue":{"title":"Ignoring a subtree","milestone":null,"user":{"id":203655,"login":"shurizzle","url":"https://api.github.com/users/shurizzle","avatar_url":"https://secure.gravatar.com/avatar/e85dca98788a0d1e58aa80fb5dcfe9d1?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"e85dca98788a0d1e58aa80fb5dcfe9d1"},"created_at":"2011-12-20T11:34:29Z","labels":[],"state":"closed","updated_at":"2011-12-20T12:57:22Z","id":2611937,"html_url":"https://github.com/kschiess/parslet/issues/61","pull_request":{"patch_url":"https://github.com/kschiess/parslet/pull/61.patch","html_url":"https://github.com/kschiess/parslet/pull/61","diff_url":"https://github.com/kschiess/parslet/pull/61.diff"},"closed_at":"2011-12-20T12:57:22Z","body":"I need to ignore a whole subtree, so i wrote a patch to ignore it using Parslet::Atoms::Base#as(nil), i think this can be a good feature :)","number":61,"url":"https://api.github.com/repos/kschiess/parslet/issues/61","comments":1,"assignee":null},"comment":{"user":{"id":2991,"login":"kschiess","url":"https://api.github.com/users/kschiess","avatar_url":"https://secure.gravatar.com/avatar/6e32b16ec35070a346dd4e08799589e5?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"6e32b16ec35070a346dd4e08799589e5"},"created_at":"2011-12-20T12:57:22Z","updated_at":"2011-12-20T12:57:22Z","id":3218401,"body":"This is backwards - .as(nil) in production code? Really? If this is serious, it should be called atom.ignore or such. \r\n\r\nAnd please write to the mailing list with an example of why you cannot use parslet without that feature. Let's discuss first.\r\n\r\nI might seem stubborn here, but I am trying hard to keep things orthogonal and small. Parslet is not about fighting complexity with more complexity. ","url":"https://api.github.com/repos/kschiess/parslet/issues/comments/3218401"},"action":"created"}