How to enable multiple query arguments in a synthetic GraphQL API

Question

I'm using Azure API management Synthetic GraphQL feature to transform a normal REST API into GraphQL one.

Let me explain the use case with example mentioned in Microsoft Learning HUB.

I have added a third query getBlogByOwnerAndTitle to existing two(already discussed in the learning hub).I want to be able to filter and return blogs based on owner and title both. I have tried making it a composite filter object and resolve it using set-graphql-resolver policy.But its not working.What I really want is to be able to filter using not just one attribute but more than one.

Thanks,Ashwin

type Comment {
    id: ID!
    owner: string!
    content: string!
}

type Blog {
    id: ID!
    title: string!
    content: string!
    comments: [Comment]!
    comment(id: ID!): Comment
}

type Query {
    getBlog(): [Blog]!
    getBlog(id: ID!): Blog
	getBlogByOwnerAndTitle(owner: string, title: string): [Blog]
}

Answer 1

Ashwin Kumar Sri Vangipuram Thanks for posting your question in Microsoft Q&A. set-graphql-resolver policy is retired and as described in the doc, you can add managed resolvers such as HTTP-based data source for GraphQL field in the schema. If you are looking to resolve getBlogByOwnerAndTitle, then owner and title are available as Arguments in context.GraphQL like described in the doc.

Here is code snippet of the resolver policy:

<http-data-source>
	<http-request>
		<set-method>GET</set-method>
		<set-url>https://data.contoso.com/api/ownertitle</set-url>
		<set-header name="Content-Type" exists-action="override">
			<value>application/json</value>
		</set-header>
		<set-body>@{ 
                        JObject jsonObject = new JObject();
                        jsonObject.Add("owner", context.GraphQL.Arguments["owner"]);
                        jsonObject.Add("title", context.GraphQL.Arguments["title"]);
                        return jsonObject.ToString();
        }</set-body>
	</http-request>
</http-data-source>

Note: this is just for reference, and I didn't have HTTP endpoint to fully validate. I hope this helps and if you face any issues, let me know.