Class BlazePersistenceDgsAutoConfiguration

java.lang.Object
com.blazebit.persistence.integration.graphql.dgs.BlazePersistenceDgsAutoConfiguration

@Configuration @Import({com.blazebit.persistence.integration.graphql.dgs.mapper.EntityViewInputObjectMapper.class,com.blazebit.persistence.integration.graphql.dgs.converter.ByteInputIdConverter.class,com.blazebit.persistence.integration.graphql.dgs.converter.ShortInputIdConverter.class,com.blazebit.persistence.integration.graphql.dgs.converter.IntegerInputIdConverter.class,com.blazebit.persistence.integration.graphql.dgs.converter.LongInputIdConverter.class,com.blazebit.persistence.integration.graphql.dgs.converter.UUIDInputIdConverter.class,com.blazebit.persistence.integration.graphql.dgs.converter.StringInputIdConverter.class}) @ImportAutoConfiguration(GraphQLEntityViewSupportFactoryAutoConfiguration.class) public class BlazePersistenceDgsAutoConfiguration extends Object
The following is a bit against the schema first DGS principle but we do it anyway since it's a lot easier to work this way than to define types twice and try to make sure they match up.
Since:
1.6.9
Author:
Christian Beikov
  • Constructor Details

    • BlazePersistenceDgsAutoConfiguration

      public BlazePersistenceDgsAutoConfiguration(EntityViewManager evm, GraphQLEntityViewSupportFactory graphQLEntityViewSupportFactory)
      The constructor creates the TypeDefinitionRegistry that is later exposed via @DgsTypeDefinitionRegistry. It is done here since we have a ordering constraint, graphQLEntityViewSupportFactory need to fill it in its create method while creating the GraphQLEntityViewSupport that is later exposed as bean.
  • Method Details

    • getSchema

      @Bean public GraphQLEntityViewSupport getSchema()
    • registry

      public graphql.schema.idl.TypeDefinitionRegistry registry()