support chain-calls

[sdbaiguanghe]

could support chain-calls? I think it is more convenient。

Before

  decoder := schema.NewDecoder()
  decoder.SetAliasTag("query")
  decoder.ZeroEmpty(true)
  decoder.IgnoreUnknownKeys(true)
 // err := decoder.Decode(dst,src)

After

   decoder := schema.NewDecoder().SetAliasTag("query").ZeroEmpty(true).IgnoreUnknownKeys(true)
  // err := decoder.Decode(dst,src)

[sdbaiguanghe]

@elithrar why check failed? what's meaning of the error information (The command "go get golang.org/x/tools/cmd/vet" failed and exited with 1 during),what should i do next?

[elithrar]

This is a build error with changes to go vet, not with your code.

I'll take a look at your PR tonight.

On Tue, Apr 26, 2016 at 2:13 AM sdbaiguanghe notifications@github.com
wrote:

@elithrar https://github.com/elithrar why check failed? what's mean of
the error information ---(The command "go get golang.org/x/tools/cmd/vet"
failed and exited with 1 during)
https://travis-ci.org/gorilla/schema/builds/125733232,what should i do
next?

—
You are receiving this because you were mentioned.

Reply to this email directly or view it on GitHub
#59 (comment)

[elithrar]

Can you write a test for this that demonstrates the usage? Helps prevent regression. Otherwise looks good.

[sdbaiguanghe]

I modified decoder_test.go for demonstrates and test the new usage . Is that what needed?

[kisielk]

Technically this breaks the API guarantee if someone has created an interface that Decoder conforms to.

[kisielk]

I think it's a pretty unlikely case though, I can't really see a reason to do that apart from in unit tests, and even then...

[kisielk]

I'm going to close this. There's really not that much benefit since there's only a few options, and it breaks the public API.