-
Notifications
You must be signed in to change notification settings - Fork 5
-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parser.Param fails if block/section has a period in it #10
Comments
Ajnasz
added a commit
that referenced
this issue
Jul 6, 2016
Helps on Github ticket #10 Always the most specific block name will win: if you search for config.param('foo.bar.baz') [foo.bar.baz] will win above [foo.bar] baz=qux and above [foo] bar.baz = qux
Hey @knightzac19! See the period-in-block-name branch for possible solutions. Hope it helps. |
I also merged master into the branch, so you can test out with the other fixes made for your issue requests! |
That worked perfectly as well. You're on a roll today. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Another small issue I found is that because you have it so that you can do block.key to get the key, if the block has a period in it , it fails to pull the key obviously. I am able to get around it by using your array method for the function.
So if I do
it will work fine, but if I use the string way,
I'll get a lovely "shootergamemode" undefined error and such.
Here's the block/section that is causing the issue in my INI file.
The text was updated successfully, but these errors were encountered: