[do not merge] PR for docs CICD test #3271

BlenderDude · 2025-06-06T21:30:28Z

No description provided.

changeset-bot · 2025-06-06T21:30:32Z

⚠️ No Changeset found

Latest commit: e615d50

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

codesandbox-ci · 2025-06-06T21:31:23Z

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

apollo-librarian · 2025-06-06T21:55:35Z

✅ Docs preview ready

The preview is ready to be viewed. View the preview

File Changes

0 new, 14 changed, 0 removed

* (developer-tools)/kotlin/v3/advanced/apollo-ast.mdx
* (developer-tools)/kotlin/v3/advanced/multi-modules.mdx
* (developer-tools)/kotlin/v3/advanced/no-runtime.mdx
* (developer-tools)/kotlin/v3/advanced/rxjava.mdx
* (developer-tools)/kotlin/v3/caching/http-cache.mdx
* (developer-tools)/kotlin/v3/caching/normalized-cache.mdx
* (developer-tools)/kotlin/v3/essentials/custom-scalars.mdx
* (developer-tools)/kotlin/v3/testing/mocking-graphql-responses.mdx
* (developer-tools)/kotlin/v3/testing/mocking-http-responses.mdx
* (developer-tools)/kotlin/v3/testing/ui-tests.mdx
* (developer-tools)/kotlin/v3/tutorial/01-configure-project.mdx
* (developer-tools)/kotlin/v3/index.md
* graphos/schema-design/federated-schemas/reference/moving-to-federation-2.mdx
* graphos/schema-design/federated-schemas/composition.mdx

Build ID: d898f6174b898714d9562e1e

URL: https://www.apollographql.com/docs/deploy-preview/d898f6174b898714d9562e1e

apollo-librarian

The pull request has 2 style issues. Please review the changes and make the necessary adjustments.

apollo-librarian · 2025-06-06T22:01:38Z

docs/source/schema-design/federated-schemas/composition.mdx

 ---

-In Apollo Federation, _composition_ is the process of combining a set of subgraph schemas into a supergraph schema:
+  In Apollo Federation, is the process of combining a set of subgraph schemas into a supergraph schema:


The sentence is grammatically incorrect and unclear. It should state what schema composition is.

Suggested change

In Apollo Federation, is the process of combining a set of subgraph schemas into a supergraph schema:

Schema composition is the process of combining a set of subgraph schemas into a supergraph schema.

apollo-librarian · 2025-06-06T22:01:39Z

docs/source/schema-design/federated-schemas/composition.mdx

+  </CodeColumns>

-One subgraph defines `Event.timestamp` as a `String`, and the other defines it as an `Int`. Composition doesn't know which type to use, so it fails.
+  One subgraph defines `Event.timestamp` as a `String`, and the other defines it as an `Int`. Composition doesn't know which type to use, so it fails.


HTML code tags (<code>) should be replaced with Markdown's backticks (`) for inline code snippets to ensure consistent formatting across the documentation site.

Suggested change

One subgraph defines `Event.timestamp` as a `String`, and the other defines it as an `Int`. Composition doesn't know which type to use, so it fails.

One subgraph defines `Event.timestamp` as a `String`, and the other defines it as an `Int`. Composition doesn't know which type to use, so it fails.

apollo-librarian

AI Style Review Summary

⚠️ This review and suggested changes are AI-generated. Please use common sense when accepting these suggestions, as they may not always be accurate or appropriate for your specific context.

The documentation has undergone extensive formatting and consistency improvements. Numerous leading spaces were removed from various elements including code blocks, headings, HTML tags, and notes to ensure proper rendering and alignment. Indentation within Mermaid diagrams and YAML code blocks was adjusted to maintain consistency, primarily to a 2-space standard. Grammatical clarity was enhanced by rephrasing an incomplete sentence and replacing 'But' with 'However' for a more formal tone. For inline code snippets, <code> tags were replaced with backticks to align with standard Markdown practices and style guide preferences, improving overall code block rendering and readability. Additionally, 'of the' was removed from a phrase for conciseness.

The pull request has 67 style issues. Please review the changes and make the necessary adjustments.

If you encounter any issues with this AI review, please reach out to Developer Experience Marketing for assistance.

apollo-librarian · 2025-06-10T18:22:33Z

docs/source/schema-design/federated-schemas/composition.mdx

 ---

-In Apollo Federation, _composition_ is the process of combining a set of subgraph schemas into a supergraph schema:
+  In Apollo Federation, is the process of combining a set of subgraph schemas into a supergraph schema:


The sentence is grammatically incomplete and unclear. It should state what 'is the process' refers to. Rephrased to clarify and improve readability.

Suggested change

In Apollo Federation, is the process of combining a set of subgraph schemas into a supergraph schema:

Schema composition is the process of combining a set of subgraph schemas into a supergraph schema in Apollo Federation:

apollo-librarian · 2025-06-10T18:22:33Z

docs/source/schema-design/federated-schemas/composition.mdx

-  composition -- "(Composition succeeds)" --> supergraph;
-  class composition tertiary;
-```
+  ```mermaid


Remove leading spaces to ensure proper code block rendering and consistency.

Suggested change

```mermaid

```mermaid

apollo-librarian · 2025-06-10T18:22:33Z

docs/source/schema-design/federated-schemas/composition.mdx

-  class composition tertiary;
-```
+  ```mermaid
+  graph TB;


Remove leading spaces to ensure proper code block rendering and consistency.

Suggested change

graph TB;

graph TB;

apollo-librarian · 2025-06-10T18:22:33Z

docs/source/schema-design/federated-schemas/composition.mdx

-```
+  ```mermaid
+  graph TB;
+    serviceA[Subgraph<br/>schema<br/>A];


Adjust indentation for consistency within the mermaid diagram. All elements in the diagram should have consistent indentation.

Suggested change

serviceA[Subgraph schema A];

serviceA[Subgraph schema A];

apollo-librarian · 2025-06-10T18:22:33Z

docs/source/schema-design/federated-schemas/composition.mdx

+  ```mermaid
+  graph TB;
+    serviceA[Subgraph<br/>schema<br/>A];
+    serviceB[Subgraph<br/>schema<br/>B];


Adjust indentation for consistency within the mermaid diagram. All elements in the diagram should have consistent indentation.

Suggested change

serviceB[Subgraph schema B];

serviceB[Subgraph schema B];

apollo-librarian · 2025-06-10T18:22:39Z

docs/source/schema-design/federated-schemas/composition.mdx

+  <Note>

-For examples of valid inconsistencies in field return types, see [Differing shared field return types](/graphos/schema-design/federated-schemas/sharing-types/#return-types).
+  For examples of valid inconsistencies in field return types, see [Differing shared field return types](/graphos/schema-design/federated-schemas/sharing-types/#return-types).


Remove leading spaces for consistency within the note.

Suggested change

For examples of valid inconsistencies in field return types, see [Differing shared field return types](/graphos/schema-design/federated-schemas/sharing-types/#return-types).

For examples of valid inconsistencies in field return types, see [Differing shared field return types](/graphos/schema-design/federated-schemas/sharing-types/#return-types).

apollo-librarian · 2025-06-10T18:22:39Z

docs/source/schema-design/federated-schemas/composition.mdx

+  For examples of valid inconsistencies in field return types, see [Differing shared field return types](/graphos/schema-design/federated-schemas/sharing-types/#return-types).

-</Note>
+  </Note>


Remove leading spaces to ensure proper rendering of the HTML tag and consistency.

Suggested change

</Note>

</Note>

apollo-librarian · 2025-06-10T18:22:39Z

docs/source/schema-design/federated-schemas/composition.mdx

+  </Note>

-Breaking composition is a helpful feature of federation! Whenever a team modifies their subgraph schema, those changes might conflict with another subgraph. But that conflict won't affect your router, because composition fails to generate a new supergraph schema. It's like a compiler error that prevents you from running invalid code. Refer to the [Composition Rules Reference](/graphos/reference/federation/composition-rules) for details.
+  Breaking composition is a helpful feature of federation! Whenever a team modifies their subgraph schema, those changes might conflict with another subgraph. But that conflict won't affect your router, because composition fails to generate a new supergraph schema. It's like a compiler error that prevents you from running invalid code. Refer to the [Composition Rules Reference](/graphos/reference/federation/composition-rules) for details.


Replaced 'But' with 'However' to maintain a more formal and professional tone in technical documentation.

Suggested change

Breaking composition is a helpful feature of federation! Whenever a team modifies their subgraph schema, those changes might conflict with another subgraph. But that conflict won't affect your router, because composition fails to generate a new supergraph schema. It's like a compiler error that prevents you from running invalid code. Refer to the [Composition Rules Reference](/graphos/reference/federation/composition-rules) for details.

Breaking composition is a helpful feature of federation! Whenever a team modifies their subgraph schema, those changes might conflict with another subgraph. However, that conflict won't affect your router, because composition fails to generate a new supergraph schema. It's like a compiler error that prevents you from running invalid code. Refer to the [Composition Rules Reference](/graphos/reference/federation/composition-rules) for details.

apollo-librarian · 2025-06-10T18:22:39Z

docs/source/schema-design/federated-schemas/composition.mdx

+  Breaking composition is a helpful feature of federation! Whenever a team modifies their subgraph schema, those changes might conflict with another subgraph. But that conflict won't affect your router, because composition fails to generate a new supergraph schema. It's like a compiler error that prevents you from running invalid code. Refer to the [Composition Rules Reference](/graphos/reference/federation/composition-rules) for details.

-## Next steps
+  ## Next steps


Remove leading spaces to ensure proper heading rendering and consistency.

Suggested change

## Next steps

## Next steps

apollo-librarian · 2025-06-10T18:22:39Z

docs/source/schema-design/federated-schemas/composition.mdx

+  ## Next steps

-Ready to compose your first supergraph? [Get started with GraphOS!](/graphos/get-started/guides/quickstart)
+  Ready to compose your first supergraph? [Get started with GraphOS!](/graphos/get-started/guides/quickstart)


Remove leading spaces for consistency.

Suggested change

Ready to compose your first supergraph? [Get started with GraphOS!](/graphos/get-started/guides/quickstart)

Ready to compose your first supergraph? [Get started with GraphOS!](/graphos/get-started/guides/quickstart)

apollo-librarian

AI Style Review Summary

⚠️ This review and suggested changes are AI-generated. Please use common sense when accepting these suggestions, as they may not always be accurate or appropriate for your specific context.

This pull request includes numerous formatting corrections, primarily by removing leading spaces to ensure correct rendering of code blocks, headings, content, admonitions, HTML tags, and shortcodes. Grammatical and stylistic improvements were also made, such as rephrasing a sentence for clarity, replacing 'of the' for conciseness, using backticks for inline code for consistency with Markdown, replacing 'take a look at' with 'consider' for conciseness, capitalizing 'Federation' for product reference, and replacing 'But that' with 'This' for better flow.

The pull request has 67 style issues. Please review the changes and make the necessary adjustments.

If you encounter any issues with this AI review, please reach out to Developer Experience Marketing for assistance.

apollo-librarian · 2025-06-10T19:00:12Z

docs/source/schema-design/federated-schemas/composition.mdx

 ---

-In Apollo Federation, _composition_ is the process of combining a set of subgraph schemas into a supergraph schema:
+  In Apollo Federation, is the process of combining a set of subgraph schemas into a supergraph schema:


The sentence is grammatically incorrect and missing a subject. Rephrased for clarity and proper sentence structure.

Suggested change

In Apollo Federation, is the process of combining a set of subgraph schemas into a supergraph schema:

Schema composition is the process of combining a set of subgraph schemas into a supergraph schema in Apollo Federation.

apollo-librarian · 2025-06-10T19:00:13Z

docs/source/schema-design/federated-schemas/composition.mdx

-  composition -- "(Composition succeeds)" --> supergraph;
-  class composition tertiary;
-```
+  ```mermaid


Remove leading spaces to ensure the code block is correctly rendered.

Suggested change

```mermaid

```mermaid

apollo-librarian · 2025-06-10T19:00:13Z

docs/source/schema-design/federated-schemas/composition.mdx

-  class composition tertiary;
-```
+  ```mermaid
+  graph TB;


Remove leading spaces to ensure the code block is correctly rendered.

Suggested change

graph TB;

graph TB;

apollo-librarian · 2025-06-10T19:00:13Z

docs/source/schema-design/federated-schemas/composition.mdx

-```
+  ```mermaid
+  graph TB;
+    serviceA[Subgraph<br/>schema<br/>A];


Remove leading spaces to ensure the code block is correctly rendered.

Suggested change

serviceA[Subgraph schema A];

serviceA[Subgraph schema A];

apollo-librarian · 2025-06-10T19:00:13Z

docs/source/schema-design/federated-schemas/composition.mdx

+  ```mermaid
+  graph TB;
+    serviceA[Subgraph<br/>schema<br/>A];
+    serviceB[Subgraph<br/>schema<br/>B];


Remove leading spaces to ensure the code block is correctly rendered.

Suggested change

serviceB[Subgraph schema B];

serviceB[Subgraph schema B];

apollo-librarian · 2025-06-10T19:00:18Z

docs/source/schema-design/federated-schemas/composition.mdx

+  <Note>

-For examples of valid inconsistencies in field return types, see [Differing shared field return types](/graphos/schema-design/federated-schemas/sharing-types/#return-types).
+  For examples of valid inconsistencies in field return types, see [Differing shared field return types](/graphos/schema-design/federated-schemas/sharing-types/#return-types).


Remove leading spaces to ensure the content is correctly rendered.

Suggested change

For examples of valid inconsistencies in field return types, see [Differing shared field return types](/graphos/schema-design/federated-schemas/sharing-types/#return-types).

For examples of valid inconsistencies in field return types, see [Differing shared field return types](/graphos/schema-design/federated-schemas/sharing-types/#return-types).

apollo-librarian · 2025-06-10T19:00:18Z

docs/source/schema-design/federated-schemas/composition.mdx

+  For examples of valid inconsistencies in field return types, see [Differing shared field return types](/graphos/schema-design/federated-schemas/sharing-types/#return-types).

-</Note>
+  </Note>


Remove leading spaces to ensure the admonition is correctly rendered.

Suggested change

</Note>

</Note>

apollo-librarian · 2025-06-10T19:00:18Z

docs/source/schema-design/federated-schemas/composition.mdx

+  </Note>

-Breaking composition is a helpful feature of federation! Whenever a team modifies their subgraph schema, those changes might conflict with another subgraph. But that conflict won't affect your router, because composition fails to generate a new supergraph schema. It's like a compiler error that prevents you from running invalid code. Refer to the [Composition Rules Reference](/graphos/reference/federation/composition-rules) for details.
+  Breaking composition is a helpful feature of federation! Whenever a team modifies their subgraph schema, those changes might conflict with another subgraph. But that conflict won't affect your router, because composition fails to generate a new supergraph schema. It's like a compiler error that prevents you from running invalid code. Refer to the [Composition Rules Reference](/graphos/reference/federation/composition-rules) for details.


Capitalize "Federation" as it refers to the product. Replace "But that" with "This" for better flow and conciseness, avoiding the slightly informal tone.

Suggested change

Breaking composition is a helpful feature of federation! Whenever a team modifies their subgraph schema, those changes might conflict with another subgraph. But that conflict won't affect your router, because composition fails to generate a new supergraph schema. It's like a compiler error that prevents you from running invalid code. Refer to the [Composition Rules Reference](/graphos/reference/federation/composition-rules) for details.

Breaking composition is a helpful feature of Federation! Whenever a team modifies their subgraph schema, those changes might conflict with another subgraph. This conflict won't affect your router, because composition fails to generate a new supergraph schema. It's like a compiler error that prevents you from running invalid code. Refer to the [Composition Rules Reference](/graphos/reference/federation/composition-rules) for details.

apollo-librarian · 2025-06-10T19:00:18Z

docs/source/schema-design/federated-schemas/composition.mdx

+  Breaking composition is a helpful feature of federation! Whenever a team modifies their subgraph schema, those changes might conflict with another subgraph. But that conflict won't affect your router, because composition fails to generate a new supergraph schema. It's like a compiler error that prevents you from running invalid code. Refer to the [Composition Rules Reference](/graphos/reference/federation/composition-rules) for details.

-## Next steps
+  ## Next steps


Remove leading spaces to ensure the heading is correctly rendered.

Suggested change

## Next steps

## Next steps

apollo-librarian · 2025-06-10T19:00:18Z

docs/source/schema-design/federated-schemas/composition.mdx

+  ## Next steps

-Ready to compose your first supergraph? [Get started with GraphOS!](/graphos/get-started/guides/quickstart)
+  Ready to compose your first supergraph? [Get started with GraphOS!](/graphos/get-started/guides/quickstart)


Remove leading spaces to ensure the content is correctly rendered.

Suggested change

Ready to compose your first supergraph? [Get started with GraphOS!](/graphos/get-started/guides/quickstart)

Ready to compose your first supergraph? [Get started with GraphOS!](/graphos/get-started/guides/quickstart)

updates

57c7fba

BlenderDude changed the title ~~updates~~ [do not merge] PR for docs CICD test Jun 6, 2025

bump

dbcaf55

BlenderDude added 2 commits June 6, 2025 17:57

tabbing for fake update

a9805c5

bump

764347c

apollo-librarian bot reviewed Jun 6, 2025

View reviewed changes

BlenderDude added 6 commits June 10, 2025 12:48

bump

07ea148

bump

336690f

bump

e0f7fdd

bump

3439649

bump

d310c15

bump

c30acc6

apollo-librarian bot reviewed Jun 10, 2025

View reviewed changes

bump

db0e71c

apollo-librarian bot reviewed Jun 10, 2025

View reviewed changes

BlenderDude added 2 commits June 11, 2025 12:23

bump

7dae9a5

bump

e615d50

	In Apollo Federation, is the process of combining a set of subgraph schemas into a supergraph schema:
	Schema composition is the process of combining a set of subgraph schemas into a supergraph schema.

	One subgraph defines `Event.timestamp` as a `String`, and the other defines it as an `Int`. Composition doesn't know which type to use, so it fails.
	One subgraph defines `Event.timestamp` as a `String`, and the other defines it as an `Int`. Composition doesn't know which type to use, so it fails.

	serviceA[Subgraph<br/>schema<br/>A];
	serviceA[Subgraph<br/>schema<br/>A];

	serviceB[Subgraph<br/>schema<br/>B];
	serviceB[Subgraph<br/>schema<br/>B];

	For examples of valid inconsistencies in field return types, see [Differing shared field return types](/graphos/schema-design/federated-schemas/sharing-types/#return-types).
	For examples of valid inconsistencies in field return types, see [Differing shared field return types](/graphos/schema-design/federated-schemas/sharing-types/#return-types).

	Ready to compose your first supergraph? [Get started with GraphOS!](/graphos/get-started/guides/quickstart)
	Ready to compose your first supergraph? [Get started with GraphOS!](/graphos/get-started/guides/quickstart)

[do not merge] PR for docs CICD test #3271

Are you sure you want to change the base?

[do not merge] PR for docs CICD test #3271

Uh oh!

Conversation

BlenderDude commented Jun 6, 2025

Uh oh!

changeset-bot bot commented Jun 6, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

⚠️ No Changeset found

Uh oh!

codesandbox-ci bot commented Jun 6, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

apollo-librarian bot commented Jun 6, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Docs preview ready

Uh oh!

apollo-librarian bot left a comment

Choose a reason for hiding this comment

Uh oh!

apollo-librarian bot Jun 6, 2025

Choose a reason for hiding this comment

Uh oh!

apollo-librarian bot Jun 6, 2025

Choose a reason for hiding this comment

Uh oh!

apollo-librarian bot left a comment

Choose a reason for hiding this comment

Uh oh!

apollo-librarian bot Jun 10, 2025

Choose a reason for hiding this comment

Uh oh!

apollo-librarian bot Jun 10, 2025

Choose a reason for hiding this comment

Uh oh!

apollo-librarian bot Jun 10, 2025

Choose a reason for hiding this comment

Uh oh!

apollo-librarian bot Jun 10, 2025

Choose a reason for hiding this comment

Uh oh!

apollo-librarian bot Jun 10, 2025

Choose a reason for hiding this comment

Uh oh!

apollo-librarian bot Jun 10, 2025

Choose a reason for hiding this comment

Uh oh!

apollo-librarian bot Jun 10, 2025

Choose a reason for hiding this comment

Uh oh!

apollo-librarian bot Jun 10, 2025

Choose a reason for hiding this comment

Uh oh!

apollo-librarian bot Jun 10, 2025

Choose a reason for hiding this comment

Uh oh!

apollo-librarian bot Jun 10, 2025

Choose a reason for hiding this comment

Uh oh!

apollo-librarian bot left a comment

Choose a reason for hiding this comment

Uh oh!

apollo-librarian bot Jun 10, 2025

Choose a reason for hiding this comment

Uh oh!

apollo-librarian bot Jun 10, 2025

Choose a reason for hiding this comment

Uh oh!

apollo-librarian bot Jun 10, 2025

Choose a reason for hiding this comment

Uh oh!

apollo-librarian bot Jun 10, 2025

Choose a reason for hiding this comment

Uh oh!

apollo-librarian bot Jun 10, 2025

Choose a reason for hiding this comment

Uh oh!

apollo-librarian bot Jun 10, 2025

Choose a reason for hiding this comment

changeset-bot bot commented Jun 6, 2025 •

edited

Loading

codesandbox-ci bot commented Jun 6, 2025 •

edited

Loading

apollo-librarian bot commented Jun 6, 2025 •

edited

Loading