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

DjangoModelFormMutation ignores input_field_name option #1037

Open
zbyte64 opened this issue Sep 12, 2020 · 2 comments · May be fixed by #1202
Open

DjangoModelFormMutation ignores input_field_name option #1037

zbyte64 opened this issue Sep 12, 2020 · 2 comments · May be fixed by #1202
Labels

Comments

@zbyte64
Copy link
Collaborator

zbyte64 commented Sep 12, 2020

  • What is the current behavior?

DjangoModelFormMutation has the option to change the input name of the mutation, but it is always set to "input" regardless of value. Like so:

class SendMessageMutation(DjangoModelFormMutation):
    message = relay.Node.Field(MessageType)

    class Meta:
        form_class = SendMessageForm
        input_field_name = "message"
@zbyte64 zbyte64 changed the title DjangoModelFormMutation ignores options DjangoModelFormMutation ignores input_field_name option Sep 12, 2020
eprikazc added a commit to eprikazc/graphene-django that referenced this issue May 18, 2021
@synic
Copy link

synic commented Sep 14, 2021

Bump. As far as I can tell, the only reference to input_field_name in the entire codebase is the one in the documentation. I don't think this feature is implemented whatsoever.

@odigity
Copy link

odigity commented Jun 17, 2022

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

Successfully merging a pull request may close this issue.

3 participants