Conditional rendering for trigger button

[phamduylong]

Linked Issue

Closes #3206

Description

Only render button wrapping around trigger if the snippet was provided

Changsets

Instructions: Changesets automate our changelog. If you modify files in /packages, run pnpm changeset in the root of the monorepo, follow the prompts, then commit the markdown file. Changes that add features should be minor while chores and bugfixes should be patch. Please prefix the changeset message with feat:, bugfix: or chore:.

Checklist

Please read and apply all contribution requirements.

• This PR targets the dev branch (NEVER master)
• Documentation reflects all relevant changes
• Branch is prefixed with: docs/, feat/, chore/, bugfix/
• Ensure Svelte and Typescript linting is current - run pnpm ci:check
• Ensure Prettier linting is current - run pnpm format
• All test cases are passing - run pnpm test
• Includes a changeset (if relevant; see above)

[changeset-bot]

🦋 Changeset detected

Latest commit: acef40d

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@skeletonlabs/skeleton-svelte	Patch

Not sure what this means? Click here to learn what changesets are.

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

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
skeleton-docs	❌ Failed (Inspect)		Feb 16, 2025 3:38pm

[vercel]

@phamduylong is attempting to deploy a commit to the Skeleton Labs Team on Vercel.

A member of the Team first needs to authorize it.

[Hugos68]

I know this has been closed, but just an observation, now that we wrap the snippet in a #if block, we can change: {@render trigger?.()} to {@render trigger()} because trigger will always be defined.

[phamduylong]

I know this has been closed, but just an observation, now that we wrap the snippet in a #if block, we can change: {@render trigger?.()} to {@render trigger()} because trigger will always be defined.

I had that in mind, but then missed it during the refactoring. Thanks for the catch mate.