-
Notifications
You must be signed in to change notification settings - Fork 39
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
Fix #47 and #70 #71
Fix #47 and #70 #71
Conversation
@@ -30,9 +30,14 @@ def test_keygroup | |||
assert_equal(%w(owner.emancu), | |||
match.value.instance_variable_get('@nested_keys')) | |||
|
|||
match = TOML::Document.parse('[ owner . emancu ]', root: :keygroup) | |||
assert_equal(%w(owner emancu), | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Extra blank line detected.
Minitest gem Minitest gem
@@ -1 +1,2 @@ | |||
citrus -v 3.0.2 | |||
minitest -v 5.7.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do you say that minitest
is better ?
Honestly I didn't use minitest
because I wanted to keep simple the gems dependencies
even for dev.
Anyways, it's ok, I just wonder why did you need it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you look on the unit::test documentation http://ruby-doc.org/stdlib-2.1.1/libdoc/test/unit/rdoc/Test/Unit.html it state If you are writing new test code, please use MiniTest instead of Test::Unit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You have a good point. 👍
Awesome PR!! Thank you very much for taking care of those issues, I was a little busy to do it. Let me know when its ready to be merged. |
On the other hand keeping |
Also I was wondering why you where using dep instead of bundler as they will only be used for contributing and most people use bundler anyway. |
I'm ok leaving In the other hand, about
|
@@ -1,7 +1,9 @@ | |||
require_relative 'helper' | |||
require_relative 'toml_examples' | |||
require 'json' | |||
require 'pp' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this needed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i forgot to remove pp
it i was trying to have a better compare view of the json and toml in case they differ but pp doesn't seem to improve much.
And i need json
to parse the json file
Thanks for the article, I see your point. |
Is it ready for merge ? On Monday, June 8, 2015, Timothee Guerin [email protected] wrote:
Emiliano Mancuso http://about.me/emancu |
It should unless you need anything else |
I added a few features trying to fix #47 and #70.
TOML::Errror
(Create TOML::Error as a base class for all errors #70)"""""""
)ValueOverwriteError
was too strict. The following was failing to parse but is suppose to work:[invalid key]
["valid key"]
so modified the grammar to be more strict. (checktest/examples/invalid/table-whitespace.toml
)If anything seems wrong, tell me and I will fix it.