VCST-5720: Expose the module GraphQL schema on its own endpoint - #25
Open
basilkot wants to merge 1 commit into
Open
VCST-5720: Expose the module GraphQL schema on its own endpoint#25basilkot wants to merge 1 commit into
basilkot wants to merge 1 commit into
Conversation
Register ScopedSchemaFactory<AssemblyMarker> and map the module schema to /graphql/skyflow, following the pattern used by other xAPI modules.
|
ksavosteev
approved these changes
Aug 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Register ScopedSchemaFactory and map the module schema to /graphql/skyflow, following the pattern used by other xAPI modules.
Description
References
QA-test:
Jira-link:
https://virtocommerce.atlassian.net/browse/VCST-5720
Artifact URL:
https://vc3prerelease.blob.core.windows.net/packages/VirtoCommerce.Skyflow_3.1005.0-pr-25-82f2.zip
Note
Low Risk
Small DI and middleware wiring only; no changes to payment or Skyflow client behavior.
Overview
The Skyflow xAPI module’s GraphQL schema is now served on its own route instead of only being built in DI.
During startup the module registers
ScopedSchemaFactory<AssemblyMarker>and, inPostInitialize, callsUseScopedSchema<AssemblyMarker>("skyflow")so clients can hit/graphql/skyflow, matching other xAPI modules. Payment registration and existing Skyflow services are unchanged.Reviewed by Cursor Bugbot for commit 82f2fd9. Bugbot is set up for automated code reviews on this repo. Configure here.