Help us understand the problem. What is going on with this article?

GraphQL Query, Mutation, 命名規則

共通

ファイル名の最後に

Query => resolver
Mutation => mutation

をつける。

〇〇_controllerも全部つけてるから、踏襲した方がいいんじゃない?(@nokontu さんからのアドバイスを採用)

  • all_
  • popular_

とかあるかも?

Query

リソース名_resolver.rb 採用
fetch_リソース名_resolver.rb

Mutation

作成

create_リソース名_mutation.rb 採用
insert_リソース名_mutation.rb
store_リソース名_mutation.rb

Laravelはstoreあるよね?...

更新

変更や更新という呼び方もある。

update_リソース名_mutation.rb 採用

論理削除はupdateなのか?!
=> そもそも論理削除はやめよう。もしあるなら
delete_リソース名_mutation.rb
これにすると思う。

削除

delete_リソース名_mutation.rb 採用
destroy_リソース名_mutation.rb

Why do not you register as a user and use Qiita more conveniently?
  1. We will deliver articles that match you
    By following users and tags, you can catch up information on technical fields that you are interested in as a whole
  2. you can read useful information later efficiently
    By "stocking" the articles you like, you can search right away
Comments
Sign up for free and join this conversation.
If you already have a Qiita account
Why do not you register as a user and use Qiita more conveniently?
You need to log in to use this function. Qiita can be used more conveniently after logging in.
You seem to be reading articles frequently this month. Qiita can be used more conveniently after logging in.
  1. We will deliver articles that match you
    By following users and tags, you can catch up information on technical fields that you are interested in as a whole
  2. you can read useful information later efficiently
    By "stocking" the articles you like, you can search right away