Skip to content

Comments

fix: [v0.2][#448] Added an override for the custom date in the mapper. The date input format has been changed#451

Merged
NuTTeR merged 1 commit intov0.2from
bugfix/v0.2/#448
Feb 24, 2026
Merged

fix: [v0.2][#448] Added an override for the custom date in the mapper. The date input format has been changed#451
NuTTeR merged 1 commit intov0.2from
bugfix/v0.2/#448

Conversation

@ilchudov
Copy link
Collaborator

Close #448

@ilchudov ilchudov added this to the R25.3 (v0.2) milestone Feb 23, 2026
@ilchudov ilchudov added the bug Something isn't working label Feb 23, 2026
@ilchudov ilchudov changed the title fix: Added an override for the custom date in the mapper. The date input format has been changed fix: [v0.2][#448] Added an override for the custom date in the mapper. The date input format has been changed Feb 23, 2026
@sonarqubecloud
Copy link

@NuTTeR NuTTeR merged commit 816b5fc into v0.2 Feb 24, 2026
26 of 29 checks passed
@NuTTeR NuTTeR deleted the bugfix/v0.2/#448 branch February 24, 2026 12:58
@github-actions github-actions bot locked and limited conversation to collaborators Feb 24, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Millisecond's value in date format "yyyy-MM-dd'T'HH:mm:ss.SSS'Z'" always setting 000 instead of some value when using mapper

2 participants