aethyr/Aethyr
2
0
Fork 0
Code Issues 281 Pull requests Projects Releases Packages Wiki Activity Actions

feat: implement standardized error message templates #321

Merged
freemo merged 1 commit from feature/m1-error-templates into master 2026-03-16 20:07:14 +00:00
Conversation 0 Commits 1 Files changed 7 +877 -25
freemo commented 2026-03-16 15:43:44 +00:00
Owner
Copy link

Summary

  • Implements Issue #296: Standardized Error Message Templates
  • Creates ValidationMessages module with 15 player-friendly error templates
  • Integrates templates into the validation pipeline (ParamMatcher, TypeChecker, ReferenceResolver)
  • Adds override mechanism for customization/localization
  • Adds usage string generation utilities

Details

This PR implements standardized error message templates for the validation framework. All 15 templates are:

  • Player-friendly (no technical jargon)
  • Consistently formatted (sentence case, proper punctuation)
  • Support keyword interpolation for dynamic values
  • Easily overridable via set_override/reset_overrides!

Testing

  • Added 42 new Cucumber scenarios with 138 steps
  • Updated existing validation pipeline tests to use new message format
  • All validation-related tests pass (128 scenarios, 530 steps)

Closes

Closes #296

## Summary - Implements Issue #296: Standardized Error Message Templates - Creates ValidationMessages module with 15 player-friendly error templates - Integrates templates into the validation pipeline (ParamMatcher, TypeChecker, ReferenceResolver) - Adds override mechanism for customization/localization - Adds usage string generation utilities ## Details This PR implements standardized error message templates for the validation framework. All 15 templates are: - Player-friendly (no technical jargon) - Consistently formatted (sentence case, proper punctuation) - Support keyword interpolation for dynamic values - Easily overridable via set_override/reset_overrides! ## Testing - Added 42 new Cucumber scenarios with 138 steps - Updated existing validation pipeline tests to use new message format - All validation-related tests pass (128 scenarios, 530 steps) ## Closes Closes #296
freemo force-pushed feature/m1-error-templates from 6bd04bbce6 to 1126534673 2026-03-16 16:57:07 +00:00 Compare
freemo force-pushed feature/m1-error-templates from 1126534673 to 54c748c4f6 2026-03-16 17:31:54 +00:00 Compare
freemo force-pushed feature/m1-error-templates from 54c748c4f6 to 123669428d 2026-03-16 20:02:34 +00:00 Compare
freemo merged commit 123669428d into master 2026-03-16 20:07:14 +00:00
freemo deleted branch feature/m1-error-templates 2026-03-16 20:07:15 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
Blocked

Cannot proceed, depends on unresolved issue

  
Duplicate

Issue is a duplicate of an existing one

  
MoSCoW/Could Have

Desirable but not necessary, included if time permits

  
MoSCoW/Must Have

Essential, project cannot ship without it

  
MoSCoW/Should Have

Important but not strictly essential

  
Points/1

Estimated effort: 1 story points

  
Points/13

Estimated effort: 13 story points

  
Points/2

Estimated effort: 2 story points

  
Points/21

Estimated effort: 21 story points

  
Points/3

Estimated effort: 3 story points

  
Points/5

Estimated effort: 5 story points

  
Points/8

Estimated effort: 8 story points

  
Priority/Backlog

Not yet prioritized

  
Priority/Critical

Must be addressed immediately

  
Priority/High

Important, should be completed soon

  
Priority/Low

Nice to have, not time-sensitive

  
Priority/Medium

Normal priority, valid and should be addressed

  
State/Completed

Issue resolved and all PRs merged

  
State/In progress

Someone is actively working on this issue

  
State/In review

Implementation complete, PR submitted for review

  
State/Paused

Work temporarily suspended, typically blocked

  
State/Unverified

Issue created but not yet reviewed by a maintainer

  
State/Verified

Maintainer confirmed valid and actionable

  
State/Wont Do

Deliberate decision not to address this issue

  
Type/Bug

A defect in existing functionality

  
Type/Epic

Large body of work broken into multiple issues

  
Type/Feature

A new capability or user story

  
Type/Legendary

Major strategic pillar composed of multiple Epics

  
Type/Task

Technical or administrative work (not bug or feature)

  
Type/Testing

Test-only work item (TDD, test infrastructure, coverage)

No labels
Blocked
Duplicate
MoSCoW/Could Have
MoSCoW/Must Have
MoSCoW/Should Have
Points/1
Points/13
Points/2
Points/21
Points/3
Points/5
Points/8
Priority/Backlog
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
State/Completed
State/In progress
State/In review
State/Paused
State/Unverified
State/Verified
State/Wont Do
Type/Bug
Type/Epic
Type/Feature
Type/Legendary
Type/Task
Type/Testing
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: aethyr/Aethyr#321
No description provided.
Delete branch "feature/m1-error-templates"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?