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

Fix #446; set max_complexity after initializers #450

Merged
merged 1 commit into from
Oct 24, 2022
Merged

Conversation

takahashim
Copy link
Collaborator

@takahashim takahashim commented Oct 24, 2022

🎩 What? Why?

#446 の修正で、max_complexityを変更するタイミングをinitializerの実行後に行うようにします。

📌 Related Issues

📋 Subtasks

  • Add CHANGELOG upgrade notes, if required
  • If there's a new public field, add it to GraphQL API
  • Add documentation regarding the feature
  • Add/modify seeds
  • Add tests
  • Another subtask

@ayuki-joto ayuki-joto merged commit bd6fc38 into develop Oct 24, 2022
@ayuki-joto ayuki-joto mentioned this pull request Oct 25, 2022
6 tasks
@takahashim takahashim deleted the fix-446 branch November 19, 2022 03:23
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

Successfully merging this pull request may close these issues.

GraphQLのAPIがエラーを返す
2 participants