Add simpler way to use Component

[CraigMacomber]

Description

Add overload and default parameters to easy simple case use of Component API

Reviewer Guidance

The review process is outlined on this wiki page.

[github-actions]

Hi! Thank you for opening this PR. Want me to review it?

Based on the diff (300 lines, 6 files), I've queued these reviewers:

• Correctness — logic errors, race conditions, lifecycle issues
• Security — vulnerabilities, secret exposure, injection
• API Compatibility — breaking changes, release tags, type design
• Performance — algorithmic regressions, memory leaks
• Testing — coverage gaps, hollow tests

How this works

• Adjust the reviewer set by ticking/unticking boxes above. Reviewer toggles alone don't trigger anything.

• Tick Start review below to dispatch the review fleet.

• After review finishes, tick Start review again to request another run — it auto-resets after each dispatch.

• This comment updates as new commits land; your reviewer selections are preserved.

• Start review

[Copilot]

Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.

[CraigMacomber]

I generally don't like overloads as they add this kind of non-type safe stuff.

In this case the other option is two differently named functions (since generic inference won't let you get away with one generic function for this)

I'm thinking maybe simply "compose" and "composeCustom". These seem fine especially given the functions are nested in a namespace already, which avoids the issue of having a top level too generic sounding compose, and makes the "custom" one not have too long of a name.

Thoughts on which is better?

[Josmithr]

I personally like the user-experience of overloads for discoverability, but I agree that in this case (especially with the proposed naming) it matters less since intellisense will surface both options for autocomplete and such.

So, I guess I have a slight preference for the overloads, given that we only need the one type-cast, but I'd be fine with either.

[CraigMacomber]

Kept the overload, but did the renames to the shorter name.

[github-actions]

🔗 No broken links found! ✅

Your attention to detail is admirable.

linkcheck output

1: starting server using command "npm run serve -- --no-open"
and when url "[ 'http://127.0.0.1:3000' ]" is responding with HTTP status code 200
running tests using command "npm run check-links"


> fluid-framework-website@0.0.0 serve
> docusaurus serve --no-open

[SUCCESS] Serving "build" directory at: http://localhost:3000/

> fluid-framework-website@0.0.0 check-links
> linkcheck http://localhost:3000 --skip-file skipped-urls.txt

Crawling...

Stats:
  294296 links
    1937 destination URLs
    2187 URLs ignored
       0 warnings
       0 errors

[github-actions]

Bundle size comparison

Base commit: ed439e5ce5b4c6e1aec2c8aff8662e8989ad270f
Head commit: 2f046969c4fc5602f335665dc6b0c4d34f116aa4

⚠️ Comparison unavailable.

The PR's CI build failed — fix the build and the comment will update once the next run succeeds.