Skip to content

Conversation

@jkebinger
Copy link
Contributor

Summary

• Add support for 'reforge.current-time' property key alongside existing 'prefab.current-time'
• Maintain backward compatibility while providing SDK compatibility with reforge naming
• Both property keys now provide identical current timestamp functionality

Changes

• Added REFORGE_CURRENT_TIME_KEY constant in ConfigRuleEvaluator
• Updated prop() method to handle both time property keys with OR condition
• Added comprehensive test cases covering both time key variants

Test plan

  • Existing tests for 'prefab.current-time' continue to pass
  • New tests verify 'reforge.current-time' works identically
  • Both keys provide current system time in milliseconds
  • Time range evaluation works correctly for both keys

This change maintains full backward compatibility while adding the requested reforge SDK compatibility.

🤖 Generated with Claude Code

This change adds compatibility for the 'reforge.current-time' property key
alongside the existing 'prefab.current-time' key. Both keys now provide
the same current timestamp functionality for SDK compatibility.

Changes:
- Added REFORGE_CURRENT_TIME_KEY constant in ConfigRuleEvaluator
- Updated prop() method to handle both time property keys
- Added comprehensive test cases for both time key variants

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
@jkebinger jkebinger requested a review from a team as a code owner September 19, 2025 22:20
Copy link
Contributor

@jdwyah jdwyah left a comment

Choose a reason for hiding this comment

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

thanks

@jkebinger jkebinger merged commit 00b74c5 into main Sep 22, 2025
4 checks passed
@jkebinger jkebinger deleted the add-reforge-current-time-support branch September 22, 2025 14:39
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.

3 participants