Repository navigation
find_by_selector should return more easily navigable / parseable data structure #71
Description
This code:
parser = CssParser::Parser.new
parser.load_string! 'a { color: hotpink; font-size: 13px; }'
parser.find_by_selector 'a'
Returns an array of one string:
["color: hotpink; font-size: 13px;"]
Is there a more easily navigable / parseable data structure we could return? For example, maybe something like:
[{:color=>["hotpink"], :font_size=>["13px"]}]
Activity
grosser commentedon Jun 22, 2016
sounds like an useful feature, I think the internal structure should exist ... you could either add a
raw: trueoption oras_hash: true... but a simpler workaround could be to dogetaaron commentedon Jun 24, 2016
That doesn't work exactly right on shorthand properties like
border:Also there are some spacing issues (we get the key
" font-size"with a leading space), and also thesplitwouldn't work on variants likecolor : hotpinkorcolor:hotpinkgrosser commentedon Jun 24, 2016
I think it produces normalized css, so spaces should not be an issue, shorthand won't work though
tres commentedon Jul 19, 2016
#72
this pull request adds a to_h instance method that will allow traversal of CSS as nested Hash objects.
don't know if that's going to get you where you need to go @getaaron , but it solves an issue for me & saw this so I thought I'd drop by & let you know about it.