Skip to content

feat(SDK-1161): add print-checks terminal screens and event vocabulary - #2584

Merged
krisxcrash merged 3 commits into
mainfrom
kw/feat/print-checks-1-terminal-screens
Aug 20, 2026
Merged

feat(SDK-1161): add print-checks terminal screens and event vocabulary#2584
krisxcrash merged 3 commits into
mainfrom
kw/feat/print-checks-1-terminal-screens

Conversation

@krisxcrash

Copy link
Copy Markdown
Contributor

Summary

First of a 5-PR stack splitting up #2572 (print payroll checks) into reviewable pieces, per feedback on that PR's size. This slice:

  • Adds printChecksEvents to src/shared/constants.ts — the event vocabulary the rest of the stack builds on.
  • Adds PrintChecksFailure and PrintChecksSummary — the two terminal screens of the upcoming print-checks flow. Both are standalone, presentational components (no API calls) that read errorMessage/documentUrl via props and emit PRINT_CHECKS_RETRY/PRINT_CHECKS_CLOSE.

Nothing in this PR is wired up to anything user-facing yet — that happens in later PRs in the stack. knip/dead-code checks may flag these as currently unused; that's expected and resolves once PR 4 (state machine) wires them in.

Stack

  1. This PR — terminal screens + events
  2. Banner (stacked on this)
  3. Form (stacked on 2)
  4. State machine / orchestrator (stacked on 3)
  5. PayrollOverview integration (stacked on 4)

Testing

  • npm run test -- --run src/components/Payroll/PrintChecks — 6 tests pass
  • npx tsc --noEmit and npm run lint:check clean

🤖 Generated with Claude Code

First slice of the print-checks feature (split out of #2572 for
reviewability): the shared event constants and the two terminal
screens of the upcoming print-checks flow, PrintChecksFailure and
PrintChecksSummary. Both are standalone, presentational components
that will be wired into a state-machine orchestrator in a follow-up PR
stacked on this one.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@krisxcrash
krisxcrash requested a review from a team as a code owner August 18, 2026 22:13

@serikjensen serikjensen left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

Comment on lines +16 to +22
<Suspense fallback={<div>Loading translations...</div>}>
<I18nLoader>
<MockBaseProvider>
<Story />
</MockBaseProvider>
</I18nLoader>
</Suspense>

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: i think there should be a global configuration for this already so we don't have to reimplement for every story?

Comment on lines +15 to +22
(Story: React.ComponentType) => (
<Suspense fallback={<div>Loading translations...</div>}>
<I18nLoader>
<MockBaseProvider>
<Story />
</MockBaseProvider>
</I18nLoader>
</Suspense>

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same on this one, i feel like this is a global config somewhere?

@krisxcrash
krisxcrash added this pull request to the merge queue Aug 20, 2026
Merged via the queue into main with commit c0df873 Aug 20, 2026
35 checks passed
@krisxcrash
krisxcrash deleted the kw/feat/print-checks-1-terminal-screens branch August 20, 2026 21:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants