recruit/candidate-decision-buttons · CandidateDecisionButtons

Decision buttons

Yes and No as equal, neutral buttons that start your own decision flow, such as asking why.

Sam Lindqvist is waiting for a decision.

Install

With your coding agentInstall RecruiterOS/recruit-ui and add yes and no buttons that ask why before a decision is saved.
With the shadcn CLIpnpm dlx shadcn@latest add RecruiterOS/recruit-ui/recruit-workflows

Props

PropTypeWhat it does
onChooserequired(decision: CandidateDecisionChoice) => voidCalled with the button a person pressed. Nothing is recorded yet: the host usually opens its own sheet or dialog to ask why, then saves.
size"sm" | "default"
stretchbooleanShare the available width between the two buttons, as in an action bar.
disabledbooleanHolds both buttons, such as while the page they sit on is loading someone else.
labelsPartial<CandidateDecisionButtonsLabels>
childrenReactNodeRendered inside the group after the buttons, usually the host's reason sheet. Events that bubble out of its portal then stop here with the buttons' own, instead of reaching a clickable card.

Data

The component takes plain values and callbacks and keeps no records of its own. Pass it yours, from the Kith data layer or from a backend you already run.