fix README: add parse:true documentation

[billychan]

I found error when I followed README to add tags as

@user.tag_list.add("awesomer, slicker") 

The result is one tag named "awesome, slicker" which is incorrect. I browsed source and found the right usage should be

@user.tag_list.add("awesomer, slicker", parse: true)
# or
@user.tag_list.add("awesomer", "slicker")

The result is correct, two tags "awesome" and "slicker"

This pull request fixed the missing part in README.

[bf4]

Can you rebase against master and force push?

[billychan]

@bf4, sure. Done.

[bf4]

Maybe add a note that this depends on the ActsAsTaggableOn.delimiter being set to ,? Also, please rebase and forced push to only one commit.

[billychan]

@bf4, sure thing! Also I want to change all of the comment style in that block from inline comment to separated lines as this line on working and the last one are too long for readability. Is that okay?

[bf4]

Sure

[billychan]

@bf4, I tried to add the dependency words but found there are several places with similar case. Doing such would looks redundant so I ended adding a general note above "#Usage". rebased against the latest master and force pushed.

[bf4]

Maybe?

alternatively, rather than passing in an array of tag arguments, you can pass in a string with a delimited list of tags to be parsed, with 'parse: true'

[bf4]

Or maybe there should just be a general section on the options hash most of the tagging methods take, separate from the general examples?

[billychan]

Nice idea. I think the alternative section is cleaner, just like the line "To preserve the order in which tags are created use acts_as_ordered_taggable" and its later section. I'll do that.

[billychan]

Hi @bf4, sorry for my late. I added quite a lot of changes on "Usage". Please take a look at first, I'll rebase it if everythings okay. Happy new year!

[bf4]

Pretty good! I might want to re-read for grammar, but content looks good.

[billychan]

Thanks!