resolver modularization

[elpum4]

Hello people, I hope you understand my question since I don't speak English very well. I have generated a project in flask that works correctly, but when modularizing, I don't know how I could use a "querytype" without having to call it so many times.

I leave you a concrete example of two resolvers... and how I call them in api.py

1-

from resources.user import user
from models.behaviour.crops import Crops
from common.helpers import parse_authorization
from ariadne import QueryType
from quart import request


query_crop = QueryType()


# Query definitions
@user.field("crops")
@query_crop.field("crops")
async def resolve_crops(_, info):
    _, bearer = parse_authorization(request)
    return await Crops(bearer=bearer).get_all()

2-

from models.behaviour.layers import Layers
from common.helpers import parse_authorization
from quart import request
from ariadne import QueryType, ScalarType, ObjectType


query_layers = QueryType()


@query_layers.field("layers")
@query_layers.field("layer")
async def resolve_layers(_, info, **kwargs):
    _, bearer = parse_authorization(request)
    return await Layers(bearer=bearer, route="layers", **kwargs).get_all()

3- Call

type_defs = load_schema_from_path(SCHEMA_DIR)
schema = make_executable_schema(
    type_defs,
    query_attch,
    query_crop,
    query_collection,
    query_field,
    query_report,
    query_season,
    query_survey,
    query_trial,
    query_user,
    query_layers,
    query_center,
    # ObjetTypes
    collection,
    field_version,
    field_survey,
    field_trial,
    node,
    survey,
    survey_layout,
    survey_plot,
    trial,
    trial_survey,
    user,
    client,
    # ScalarTypes
    extent,
    coordinates,
    layouts_metadata,
    corners,
    init_coordinate,
    properties,
    tag,
    field_geometry,
    date_all,
    survey_metadata,
    survey_tags,
    report_properties,
    report_id,
)

what I'm looking for, is to reduce that list of "query_types" to maybe a class or something similar.

[rafalp]

what I'm looking for, is to reduce that list of "query_types" to maybe a class or something similar.

Did you consider Ariadne GraphQL Modules?

[elpum4]

In this way, I could not make the schemas in .graphql, right?

[rafalp]

You can mix both, some types being in .graphql files, and some in classes.

[elpum4]

Ok, I'll try that, thank you very much!

[rafalp]

Can you show GraphQL schema? I don't understand why you are setting same resolver to multiple fields:

@query_layers.field("layers")
@query_layers.field("layer")

You don't have to call parse_authorization(request) in resolvers. Doing it in custom context_value instead is recommended for this:

_, bearer = parse_authorization(request)

context_value = {
    "request": request,
    "bearer": bearer,
}

graphql_sync(..., context_value=context_value)

Then in resolvers:

@query_layers.field("layers")
@query_layers.field("layer")
async def resolve_layers(_, info, **kwargs):
    return await Layers(bearer=info.context["bearer"], route="layers", **kwargs).get_all()

[elpum4]

My schemas, come from ".graphql" files...

extend type Query {
  """
    Query all layers, you can filter by (Example: collection_id)
  """
  layers(collection_id:ID): [Layer]
  layer(layer_id:ID!): Layer
}

type Layer {
  extent: Extent
  field_version_id: String
  field_id: String
  category: String
  description: String
  title: String
  crop: Crops
  geom_type: String
  id: String
  is_multiseason: Boolean
  group_id: String
  field_version: FieldVersionLayer
  trial_id: String
  collection_id: String
}

type FieldVersionLayer{
  season: SeasonLayer
}
type SeasonLayer {
  nomenclature: String
  status: String
  season_id: String
}

other file...

extend type Query {
  crops: [Crops]
}

type Crops {
  crop_id: ID
  crop_name: String
}

[elpum4]

Thanks for the bearer

[rafalp]

This resolver:

async def resolve_layers(_, info, **kwargs):
    _, bearer = parse_authorization(request)
    return await Layers(bearer=bearer, route="layers", **kwargs).get_all()

Will not work for this field:

  layer(layer_id:ID!): Layer

Because resolver returns list of layers, and layer field expects one layer

[elpum4]

If it works, since the response of the API changes according to the url where it points, And returns a list or a layer