Skip to content

feat: Add conditional blocks to salary change message template#320

Merged
MarconLP merged 15 commits intomainfrom
timgl/salary-change-template
Apr 2, 2026
Merged

feat: Add conditional blocks to salary change message template#320
MarconLP merged 15 commits intomainfrom
timgl/salary-change-template

Conversation

@timgl
Copy link
Copy Markdown
Collaborator

@timgl timgl commented Apr 2, 2026

Problem

When communicating salary changes, different employees need different messaging depending on whether their raise came from a benchmark update, a level/step increase, both, or a location factor change. Previously the template was a single static message with no conditional logic.

Changes

  • Updated the default salary communication template with detailed messaging for each raise scenario (benchmark + level/step increase, full benchmark only, partial benchmark/recalibration, location factor increase)
  • Added {#if condition}...{/if} syntax to the template engine supporting &&, ||, and ! operators
  • Added computed boolean conditions: benchmarkChanged, levelOrStepIncreased, levelOrStepSame, levelOrStepDecreased, locationFactorIncreased, locationFactorChanged
  • Updated the template editor dialog to show available conditions with tooltip descriptions

How did you test this code?

I'm an agent — I verified the code typechecks cleanly (no new TS errors) but have not manually tested the UI.

🤖 LLM context

Authored by Claude Opus 4.6 via Conductor.

Update the default salary communication template with detailed
messaging for different raise scenarios (benchmark + level/step,
full benchmark, partial benchmark, location factor changes).

Add {#if condition}...{/if} syntax to the template engine with
support for &&, ||, and ! operators.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@timgl timgl requested a review from MarconLP as a code owner April 2, 2026 00:27
@MarconLP MarconLP merged commit 57e3f90 into main Apr 2, 2026
13 checks passed
@MarconLP MarconLP deleted the timgl/salary-change-template branch April 2, 2026 13:35
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