feat: Add conditional blocks to salary change message template#320
Merged
feat: Add conditional blocks to salary change message template#320
Conversation
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>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
MarconLP
approved these changes
Apr 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
{#if condition}...{/if}syntax to the template engine supporting&&,||, and!operatorsbenchmarkChanged,levelOrStepIncreased,levelOrStepSame,levelOrStepDecreased,locationFactorIncreased,locationFactorChangedHow 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.