You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to the documentation at rubydoc.info, parseconfig 0.5.2 should provide parsed config values by indexing into a ParseConfig object. The snippet in question is under "synopsis":
However, this method doesn't seem to exist on the ParseConfig object as it stands. In irb:
> require 'parseconfig'
> config = ParseConfig.new("local-file.conf")
> config['key'] # expect "value"
NoMethodError: undefined method `[]' for #<ParseConfig:0x007f99a481e0d0>
from (irb):4
from /usr/local/bin/irb:12:in `<main>'
Is this a documentation problem (out of date) or an issue with parseconfig itself? If it's the latter, I'll be happy to submit a pull request fixing the problem; I'm just not sure whether it's the documentation at fault, or how to fix it if it is.
The text was updated successfully, but these errors were encountered:
It would make sense to me to be able to call "config['groupX']['paramX']" ... but I'll be honest, I've been coding Python for a long time now and haven't touched ruby in years. I don't really know where to start to implement that in ruby.
Any suggestions, or pull requests would be appreciated... just keep in mind that any changes need to maintain compatibility with current functionality.
Tests would be awesome. Like I said its been a while since I've actively worked in Ruby which is the main reason I haven't made many improvements to this project. That and, there haven't been many requests from the community. Tests would be great however.
According to the documentation at rubydoc.info, parseconfig 0.5.2 should provide parsed config values by indexing into a ParseConfig object. The snippet in question is under "synopsis":
However, this method doesn't seem to exist on the ParseConfig object as it stands. In irb:
Is this a documentation problem (out of date) or an issue with parseconfig itself? If it's the latter, I'll be happy to submit a pull request fixing the problem; I'm just not sure whether it's the documentation at fault, or how to fix it if it is.
The text was updated successfully, but these errors were encountered: