OneToMany vs OneToOne (Docs)

[kingsleyzissou]

I'm not entirely sure if this is a bug or possibly something that might need to be clarified in the docs.

Given this example here from the docs a oneToMany annotation will create a field on the type, so:

"""model"""
type User {
  id: ID!
  """@oneToMany(field: 'author')"""
  posts: [Post]!
}

"""@model"""
type Post {
  id:ID!
  text: String!
}

Will generate the following:

"""@model"""
type Post {
  id: ID!
  text: String!
  author: User
}

When I inspect the schema on the server that all checks out.

The docs say something similar about the oneToOne relationship, but inspecting the schema on the server,
I find that it is creating the field on the type that has the annotation, so the following:

"""
@model
"""
type Note {
  _id: GraphbackObjectID!
  title: String!
  description: String!
  """
  @oneToOne(field: 'note')
  """
  comment: Comment!
}

"""
@model
"""
type Comment {
  _id: GraphbackObjectID!
  title: String!
  description: String!
}

And the result on the server is this:

type Note {
  _id: GraphbackObjectID!
  title: String!
  description: String!
  comment: Comment!
  _lastUpdatedAt: GraphbackTimestamp
  _version: Int
}

type Comment {
  _id: GraphbackObjectID!
  title: String!
  description: String!
  _lastUpdatedAt: GraphbackTimestamp
  _version: Int
}

Is there an undocumented change I am missing, or am I making a mistake with my annotations?

[machi1990]

Automatically generated comment to notify maintainers
/cc @craicoverflow, @machi1990, @wtrocki

[kingsleyzissou]

I noticed the same applies when I am trying to generate schema for the oneToOne relationships in the Offix cli. The field is generated for the type that has the annotation, is this expected behaviour.

The PR is (I haven't pushed the changes yet):
aerogear/offix#899

[craicoverflow]

Thank you for pointing this out. The @oneToOne annotation does not have a field argument..these docs are wrong. Eventually it will have, if we add bidrectional query capacity on a 1:1 (see #930).

I will remove this from the documentation.