Control foreign field name for @hasMany

[johnf]

Is this feature request related to a new or existing Amplify category?

api

Is this related to another service?

No response

Describe the feature you'd like to request

This is a bug/feature

I can set the index on hasMany as follows

type User {
  is: ID!
  posts: [Posts] @hasMany(indexName: "byUser")
}

type Post {
  id: ID!
  userId: ID! @index(name: "byUser")
  user: User @belongsTo(fields: "userId")
}

If I look at the query generated for Post it will look something like

   query GetPost($id: ID!) {
      getPost(id: $id) {
        id
        userId
        user {
          id
          posts {
            nextToken
          }                                                                                                                                                                         
        }                                                                                                                                                                                    
        createdAt                                                                                                                                                                            
        updatedAt                                                                                                                                                                            
        userPostsId                                                                                                                                                                        
      }                                                                                                                                                                                      
    }                               

Notice that userPostsId is being created when it isn't needed.

Describe the solution you'd like

I would suggest two changes

• Add the ability to set the foreign key name in hasMany
• If an index is references in HasMany then use the fields for that index as the foreign key

Describe alternatives you've considered

Living with the autogenerated key names but this makes the code not as neat as it can be for my use case

Additional context

@edwardfoyle this looks like it might be similar to #8557

Is this something that you'd be interested in working on?

• 👋 I may be able to implement this feature request
• ⚠️ This feature might incur a breaking change

[lazpavel]

@johnf you should be able to avoid the generation of the extra field by adding the fields attribute to the hasMany directive as in

type User @model {
  is: ID!
  posts: [Posts] @hasMany(indexName: "byUser", fields: ["is"])
}

Please let us know if this solved it for you

[josefaidt]

Closing due to inactivity. @johnf if you are still experiencing this issue please reply back to this thread and we can re-open to investigate further 🙂

[github-actions]

This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs.

Looking for a help forum? We recommend joining the Amplify Community Discord server *-help channels for those types of questions.