GraphQL @connection improvments

[Hideman85]

There is still some useful case not supported yet that not permit me to deploy my model. There is some example:

type A
@model
{
  id: ID!
}

type B
@model
{
  id: ID!
  objAID: ID
  objA: A @connection(fields: ["objAID"])
  # InvalidDirectiveError: All fields provided to an @connection must be non-null scalar or enum fields.
  # Why are we not able to have a check if it's null just return a null object?
}

union Obj = A | B
type C
@model
{
  id: ID!
  objID: ID!
  obj: Obj! @connection(fields: ["objID"])
  # InvalidDirectiveError: Could not find an object type named Obj.
  # By prefixing the id with the typename we can fetch in the correct table so why not supporting that?
  # specially because you don't allow us to manage IDs ourself!
}

[edwardfoyle]

The latest version of the CLI now supports nullable connection fields. For your other request about supporting union types, see: aws-amplify/amplify-category-api#450

[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.