Skip to content

ISSUE #3 Improved Error System and User Feedback #3

@Jeck0v

Description

@Jeck0v

Problems

  • Uninformative error messages: Errors such as "Parse error: Expected athena_file rule" provide no actionable context.
  • No error location: Pest parser errors do not include line/column numbers
  • Context switching: Users must guess where the issue lies in their .ath file, slowing debugging.
  • Incomplete validation: Critical checks such as port conflicts between services are missing.

### Examples of Enhanced Errors

Error: Parse error at line 15, column 23: Expected 'END SERVICE'
   |
15 | SERVICE backend
   |            ^ Missing END SERVICE for this service block
   |

Suggestion: Add 'END SERVICE' after your service configuration


Error: Port conflict detected: Port 8080 is used by both 'frontend' and 'backend'
Suggestion: Use different host ports, e.g., 8080:80 and 8081:80

Focus On

  • Error messages must include line and column numbers
  • Automatic suggestions for possible fixes are provided
  • Port conflict detection is implemented
  • Service reference validation is complete
  • Comprehensive tests exist for all error cases

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions