I'm not super familiar with this, but doesn't schema require that the struct have exported fields (capitalized names)
You can get around that by capitalizing the names, and then giving them a tag like in the example here:
http://www.gorillatoolkit.org/pkg/schema
So
type User struct{
Email string `schema:"email"`
Password string `schema:"password"`
Created string `schema:"created"`
> 2015/01/12 04:39:50 registrationHandler: map[email:[ima...@go.lang] password:[changeme] created:[now]]
> 2015/01/12 04:39:50 &{email: password: created:}
> 2015/01/12 04:39:50 Email is
>
> In the terminal where I call curl I just get...
> HTTP/1.1 200 OK
> Access-Control-Allow-Origin: *
> Date: Mon, 12 Jan 2015 04:39:50 GMT
> Content-Length: 29
> Content-Type: text/plain; charset=utf-8
>
> &{email: password: created:}
>
>
>
> At this point I've been troubleshooting for about the last 5 hours with no luck.
> I'm really hoping someone has an idea or sees something obvious I've missed.
> Otherwise I'll have to go back to isolating each field individually using FormValue or something, but I hate that idea for a myriad of reasons.
>
> I'm kind of fond of the validate input by contract idea and importing directly to an object/struct and complaining if it fails.
> Not really sure if that's idiomatic in go or not though.
>
> Thanks!
>
>
>
>
>
> --
> You received this message because you are subscribed to the Google Groups "golang-nuts" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
golang-nuts...@googlegroups.com.
> For more options, visit
https://groups.google.com/d/optout.