fix: export ActionButton component from sistent

[KhushamBansal]

Notes for Reviewers

This PR fixes #

Signed commits

• Yes, I signed my commits.

Summary by CodeRabbit

• New Features
  • Added the ActionButton component to the package’s public exports for use in applications.
  • Added public access to ActionButtonProps and Option types, improving support for type-safe customization and configuration.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: ea9d8ce0-cdf4-4044-a42d-1d3e4d0a79fc

📥 Commits

Reviewing files that changed from the base of the PR and between d0e7370 and 8fb3846.

📒 Files selected for processing (3)

• src/custom/ActionButton/ActionButton.tsx
• src/custom/ActionButton/index.tsx
• src/index.tsx

🚧 Files skipped from review as they are similar to previous changes (1)

• src/index.tsx

---

📝 Walkthrough

Walkthrough

The package now publicly exports ActionButton, ActionButtonProps, and Option through the package entry point. Option is now an exported interface.

Changes

ActionButton export

Layer / File(s)	Summary
Package entry point export src/custom/ActionButton/ActionButton.tsx, src/custom/ActionButton/index.tsx, src/index.tsx	Exports the Option interface, re-exports ActionButtonProps and Option, and exposes ActionButton with both types from the package entry point.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested reviewers: rishiraj38

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the main change: exporting the ActionButton component from sistent.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[Katotodan]

Adding this export to src/index.tsx solves the problem, but I think the code could be cleaner and better scoped if we added the export to src/custom/index.ts instead (and still keep the export from src/custom/index.tsx).

Currently, it's exported from src/custom/index.tsx. If we add the export to src/custom/index.ts, I believe it should still work while keeping the change more localized and organized.

I could be mistaken, though.

[ishwar170695]

LGTM. This follows the existing explicit export pattern used in src/index.tsx for components affected by the declaration bundling issue.

[ishwar170695]

Adding this export to src/index.tsx solves the problem, but I think the code could be cleaner and better scoped if we added the export to src/custom/index.ts instead (and still keep the export from src/custom/index.tsx).

Currently, it's exported from src/custom/index.tsx. If we add the export to src/custom/index.ts, I believe it should still work while keeping the change more localized and organized.

I could be mistaken, though.

I think the explicit export in src/index.tsx is intentional here. The existing comments indicate it's a workaround for rollup-plugin-dts dropping declarations behind export * from './custom', so I'd lean toward keeping it consistent with the existing pattern.

[banana-three-join]

I believe it also needs the typing exported

[KhushamBansal]

I believe it also needs the typing exported

@banana-three-join Thanks for reviewing. I have updated the PR.

[banana-three-join]

Ty! LGTM