Fix #37894: Update yaml doc for composite transform changes

[liferoad]

Issue: apache#37894

This PR updates the YAML documentation to reflect the implicit input chaining feature for composite transforms (introduced in PR apache#37861).

Changes

• Added new section "Implicit Input Chaining for Composite Transforms" to yaml-schema.md
• Documented that composite transforms can now omit explicit input specifications on sub-transforms
• Added examples showing implicit chaining vs explicit chaining

Testing

• Documentation only change, no code changes

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the YAML schema documentation to reflect a recently introduced feature allowing implicit input chaining within composite transforms. The changes aim to provide clear guidance and examples for users on how to leverage this new functionality, improving the usability and understanding of composite transform configurations.

Highlights

• Documentation Update: A new section, 'Implicit Input Chaining for Composite Transforms', was added to the yaml-schema.md documentation.
• Composite Transform Behavior: The documentation now clarifies that sub-transforms within a composite type can omit explicit input specifications, enabling automatic chaining.
• Examples Provided: New examples illustrate both implicit and explicit input chaining for composite transforms, enhancing clarity for users.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩