Reuse object fields as input_object fields in Absinthe

I have a absinthe object type like that:

defmodule ContentProxyGraphql.Schema.ObjectTypes.Content do
  use Absinthe.Schema.Notation
  use Absinthe.Relay.Schema, :modern

  import_types Absinthe.Type.Custom

  object :content do
    field :type_of, non_null(:string)
    field :name, non_null(:string)
    field :date_created, non_null(:datetime)
    field :date_modified, non_null(:datetime)
    field :identifier, non_null(:identifier)
    field :publisher, :publisher
  end

  object :identifier do
    field :type_of, non_null(:string)
    field :property_id,  non_null(:string)
    field :value, non_null(:string)
  end

  object :publisher do
    field :type_of, non_null(:string)
    field :name, non_null(:string)
  end

end

In my schema.ex, I have the query

query do


    field :contents, list_of(:content) do
      resolve &Resolvers.Resources.Content.list/3
    end

  end

Now I’m creating the mutation

mutation do 
  field :create_content, type: :content do
    arg :typeOf, non_null(:string)
    arg :name, non_null(:string)
    arg :dateCreated, non_null(:datetime)
    arg :dateModified, non_null(:datetime)

    resolve &Resolvers.Resources.Content.create/3
  end
end

In my mutation I intend to add arg :identifier and arg :publisher. According to absinthe documentation (https://hexdocs.pm/absinthe/complex-arguments.html#content) I have to create a input_object :indentifier and a input_object :publisher with their fields, which are the same of respective object :identifier and object :publisher.

Is there a way to reuse object fields inside input_object? I’m trying it to avoid code duplication, in other words, I would like to avoid

input_object :identifier do 
    field :type_of, non_null(:string)
    field :property_id,  non_null(:string)
    field :value, non_null(:string)
end

@benwilson512 FYI

1 Like

there is a import_fields function now so you can do inheritance on types. not a perfect solution but way better than not having it at all

https://hexdocs.pm/absinthe/Absinthe.Schema.Notation.html#import_fields/2

actually interfaces might be more appropriate https://hexdocs.pm/absinthe/Absinthe.Type.Interface.html

Hi @dylan-chong,
first of all, thank you to enjoin this issue :smiley: :smiley:

import_fields is intended for to keep schema.ex small, avoiding to write all of your graphl queries in the same file. So, you can create many object types whit their query in different files and register them inside query block in schema.ex

let me show you my case:

defmodule ContentProxyGraphql.Schema do
  use Absinthe.Schema

  import_types ContentProxyGraphql.Schema.ObjectTypes.Content
  import_types ContentProxyGraphql.Schema.ObjectTypes.Question

  query do
    import_fields :content_queries
    import_fields :question_queries
  end

  mutation do
    import_fields :content_mutations
  end
end

As you can see, I have two object types in separated files (keeping code organized) and I import all of them inside my schema.ex

Interface is intended to an object type guarantees that it defines the same fields and arguments that the interface does.
It is interesting to avoid developers from making mistakes on object type definition and it is useful to able to fetch different object types in the same query https://graphql.org/learn/schema/#interfaces

Not sure if you ever got around testing it, but it actually works to use import_fields