Skip to content

Fix #635: Time_period cast to String does not follow the time_period_output_format#636

Open
mla2001 wants to merge 6 commits intomainfrom
cr-635
Open

Fix #635: Time_period cast to String does not follow the time_period_output_format#636
mla2001 wants to merge 6 commits intomainfrom
cr-635

Conversation

@mla2001
Copy link
Contributor

@mla2001 mla2001 commented Mar 27, 2026

Summary

  • Time period string representation is now formatted as time_period_output_representation.
  • Minor fix on vtl format anual representation (YYYY -> YYYYA).

Checklist

  • Code quality checks pass (ruff format, ruff check, mypy)
  • Tests pass (pytest

@mla2001 mla2001 self-assigned this Mar 27, 2026
@mla2001 mla2001 requested review from a team and albertohernandez1995 March 27, 2026 13:54
@mla2001 mla2001 linked an issue Mar 27, 2026 that may be closed by this pull request
2 tasks
@mla2001 mla2001 changed the title Fix #635 Fix #635: Time_period cast to String does not follow the time_period_output_format Mar 27, 2026
Copy link
Contributor

@albertohernandez1995 albertohernandez1995 left a comment

Choose a reason for hiding this comment

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

Looks good!

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.

Fix Time_period cast to String does not follow the time_period_output_format

2 participants