Skip to content
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

html/template: How to bind nested structs from form data? #2746

Open
chokoGtr opened this issue Feb 7, 2025 · 0 comments
Open

html/template: How to bind nested structs from form data? #2746

chokoGtr opened this issue Feb 7, 2025 · 0 comments

Comments

@chokoGtr
Copy link

chokoGtr commented Feb 7, 2025

I'm trying to bind form data to nested structs, but I'm not sure if I'm doing it correctly. Is there a recommended way to handle form binding with nested structs using the standard library?

My Use Case
I have a form structure with nested fields that I want to bind to corresponding nested structs:

type UserInfo struct {
    Name string   `form:"name"`
    Sex string   `form:"sex"`
}

type UserGroup struct {
    Men []UserInfo `form:"men"`
    Women   []UserInfo `form:"women"`
}

type UserResults struct {
    Win          UserGroup `form:"win"`
    Lose UserGroup `form:"lose"`
}

func handler(w http.ResponseWriter, r *http.Request) {
    form := &UserResults{}
    if err := c.Bind(form); err != nil {
	// error handle
    }
    // Values are not bound to nested structs
}

What I've Tried
I've attempted to use dot notation in the form field names:

<form method="POST">
    <input type="number" name="win.men[0].name" value="john">
    <input type="number" name="win.men[0].sex" value="1">
</form>

Questions

  1. Is there a built-in way to handle nested struct binding with the standard library?
  2. If yes, what is the correct naming convention for form fields?
  3. Is there any documentation I might have missed about this topic?

Environment

  • Go version: 1.22

Any guidance or best practices would be greatly appreciated. If this functionality isn't currently supported, would it be worth considering as a feature request?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant