Mathias Polligkeit

This still seems to be an issue. Simple example: ```elixir field :pets, list_of(:pet) do arg :kind, :string, default_value: "dog" resolve &Resolvers.Pet.list_pets/2 end ``` ```bash mix absinthe.schema.sdl ``` Results in: ```graphql...

Regarding the last point about the account recovery, I didn't have the field configured for recovery. The other issues are still there.

It seems like this is not only an issue with identifiers within arrays. When I set up an ordinary array field like this: ```json { "secondary_emails": { "type": "array", "title":...

I also tried mapping the name from `traits.secondary_emails.0` to `traits.secondary_emails[0]`, but that still wipes out all values on submit

I think a more common way to represent arrays in HTML forms is the use of square brackets in input names: ```html ``` Which would result in: ```json { "emails[]":...

Did you by any chance have another look into what would be involved to fix this? We're handling the array field updates outside of the settings flow via the admin...

While a self-service account deletion flow can be useful in some cases, in more complex setups it wouldn't suffice. Think of a distributed system where user data must be deleted...

> What do you think about making this select/option types? It would also allow us to e.g. add labels (for translation) to the options if that ever becomes a thing....

> It would also allow us to e.g. add labels (for translation) to the options if that ever becomes a thing. If you want to add labels, this couldn't be...

Something like this? ```json { "type": "select", "group": "default", "attributes": { "name": "some_trait", "node_type": "select", "options": [ {"label": "Some value", "value": "some_value"}, {"label": "Some other value", "value": "some_other_value"} ], "value":...