Skip to content

fragmentName not exposed in RequestSpec for GraphqlClient. v1.3.2 #1050

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
devon-brazier opened this issue Aug 30, 2024 · 1 comment
Closed
Labels
status: duplicate A duplicate of another issue

Comments

@devon-brazier
Copy link

I cannot see the fragmentName function that is in the documentation.
public interface RequestSpec {
RequestSpec operationName(@nullable String operationName);

    RequestSpec variable(String name, @Nullable Object value);

    RequestSpec variables(Map<String, Object> variables);

    RequestSpec extension(String name, @Nullable Object value);

    RequestSpec extensions(Map<String, Object> extensions);

    RequestSpec attribute(String name, Object value);

    RequestSpec attributes(Consumer<Map<String, Object>> attributesConsumer);

    RetrieveSyncSpec retrieveSync(String path);

    RetrieveSpec retrieve(String path);

    RetrieveSubscriptionSpec retrieveSubscription(String path);

    ClientGraphQlResponse executeSync();

    Mono<ClientGraphQlResponse> execute();

    Flux<ClientGraphQlResponse> executeSubscription();
}
@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Aug 30, 2024
@bclozel
Copy link
Member

bclozel commented Aug 30, 2024

Sorry about that, this was a documentation problem that we fixed recently.
We only added fragment support so far on the tester, as adding on all clients was more involved and the use case requested by the community was around testing.

This was fixed in #1042

@bclozel bclozel closed this as not planned Won't fix, can't repro, duplicate, stale Aug 30, 2024
@bclozel bclozel added status: duplicate A duplicate of another issue status: waiting-for-internal-feedback An issue that needs input from a member or another Spring Team and removed status: waiting-for-triage An issue we've not yet triaged status: waiting-for-internal-feedback An issue that needs input from a member or another Spring Team labels Aug 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: duplicate A duplicate of another issue
Projects
None yet
Development

No branches or pull requests

3 participants