Problem
ion.st files generated from Python specifications do not currently track the dialect hash or version used to generate them. This means there is no way to determine whether a generated file is up to date with the current dialect, leading to potential staleness issues.
Impact
- Generated
ion.st files can silently become out of date when the Python dialect or generation logic changes.
- There is no automated way to detect or flag stale generated files.
- Users may unknowingly rely on outdated specifications.
Proposed Solution
Implement versioning for generated ion.st files. This could include:
- Embedding a dialect hash and/or version identifier in the generated file (e.g., as a header comment or metadata field).
- Adding a validation step that checks whether the embedded hash/version matches the current dialect.
- Providing a mechanism to regenerate out-of-date files when a mismatch is detected.
🤖 Generated with Claude Code
Problem
ion.stfiles generated from Python specifications do not currently track the dialect hash or version used to generate them. This means there is no way to determine whether a generated file is up to date with the current dialect, leading to potential staleness issues.Impact
ion.stfiles can silently become out of date when the Python dialect or generation logic changes.Proposed Solution
Implement versioning for generated
ion.stfiles. This could include:🤖 Generated with Claude Code