Bug
With calendar_year_offset: after in frontmatter, fiscal-period literals like FQ1 still resolve as if the directive were before (the default). Either the after branch is unimplemented or it has no effect on the year label.
Repro
---
fiscal_year_starts: Feb 15
calendar_year_offset: after
---
a = Q1
b = FQ1
Expected
b = FQ1 resolves to FY 2027 — calendar_year_offset: after labels the fiscal year by the later of the two calendar years it spans (the FY that opens 2026-02-15 ends in calendar 2027 and is therefore FY 2027 under `after`).
Actual
FQ1 labels by the default `before` policy (FY 2026 in this repro), i.e. calendar_year_offset: after is a no-op.
Notes
Filed by the CalcMark Web editor maintainer; fix being investigated in parallel.
Bug
With
calendar_year_offset: afterin frontmatter, fiscal-period literals likeFQ1still resolve as if the directive werebefore(the default). Either theafterbranch is unimplemented or it has no effect on the year label.Repro
Expected
b = FQ1resolves to FY 2027 —calendar_year_offset: afterlabels the fiscal year by the later of the two calendar years it spans (the FY that opens 2026-02-15 ends in calendar 2027 and is therefore FY 2027 under `after`).Actual
FQ1labels by the default `before` policy (FY 2026 in this repro), i.e.calendar_year_offset: afteris a no-op.Notes
end of/start ofoperators #140 (Period literals Q/FQ/FY/CY), feat: relative date math (next Friday, 2 weeks ago, fiscal quarters) #119 (fiscal quarters), feat: DateSpan type — period membership, as fiscal/calendar conversion #126 (DateSpan), Period vs Duration in function arguments — shouldover Q1reject or coerce? #143 (Period in functions). None touch thecalendar_year_offsetlabel policy.Filed by the CalcMark Web editor maintainer; fix being investigated in parallel.