Azure / Azure/apiops

[FEATURE REQ] Resolver configured with Synthetic GraphQL is not extracted via Extractor Pipeline

Open
#510 2 comments 0 reactions 1 assignee Claimed by @guythetechie View on GitHub
enhancement
Dominant language
C#
Stars
448
Forks
247
PR merge metrics
No merged PRs in 30d

Description

### Release version

ApiOps Tool Kit v4.6.0

### Describe the bug

On working with GraphQL Api options, Found that Resolver configured with Synthetic GraphQL is not extracted via Extractor Pipeline. Extractor pipeline extracts apiinformation and specification.graphql only from GraphQL Apis.

### Expected behavior

Extractor Pipeline should extract Resolver along with api information and specification.graphql for GraphQL Apis

### Actual behavior

Extractor Pipeline does extract Resolver configured with GraphQL Api

### Reproduction Steps

1. Add GraphQL Api with schema and Resolver configuration using Synthetic Api Import options.
2. Run the Extractor
syntheticgraphql

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.