Preserve one-off fee period dates - #6198
Conversation
## Context Offset-bearing one-off fee periods could display different calendar dates across invoice surfaces. ## Description Preserve the dates expressed by add-on timestamps in exports and invoice details. Signed-off-by: lago-claude-ai-agent[bot] <297187938+lago-claude-ai-agent[bot]@users.noreply.github.com>
|
Held: CI is not green on this PR; not reviewed. Re-run CI, then re-review. Checks: https://github.com/getlago/lago-api/pull/6198/checks |
|
Impediment Where I stopped: I stopped at validation and restored this revise pass's working-tree edits. Why: The required full What would unblock me: Provide a checkout with a green full RuboCop baseline and the |
Signed-off-by: lago-claude-ai-agent[bot] <297187938+lago-claude-ai-agent[bot]@users.noreply.github.com>
|
|
HOLD: invoice-detail mode is stored in query-global GraphQL context, so it can leak to unrelated sibling fields in the same operation.
|
## Context Invoice-detail formatting used query-global context and could affect add-on periods returned by sibling root fields. ## Description Scope formatting to the single-invoice field, cover sibling isolation, and restore unrelated schema annotations. Signed-off-by: lago-claude-ai-agent[bot] <297187938+lago-claude-ai-agent[bot]@users.noreply.github.com>
|
|
HOLD: amend or squash |
Add-on and one-off fee periods now keep the calendar dates expressed by offset-bearing timestamps in CSV exports and invoice detail responses, matching invoice PDFs. Frontend write-path normalization remains out of scope.