Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(components/datetime): resources strings for default calculators are not resolved in the service #2536

Merged
merged 1 commit into from
Jul 23, 2024

Conversation

Blackbaud-SteveBrush
Copy link
Member

AB#2930286

BREAKING CHANGE

Resources strings for the default calculators' shortDescription property are resolved in the date range picker's template, but any consumers expecting the shortDescription values to be resolved in the SkyDateRangeService will need to change assertions in their unit tests.

@Blackbaud-SteveBrush Blackbaud-SteveBrush added the risk level (author): 3 This change has a moderate chance of introducing a bug label Jul 22, 2024
@Blackbaud-SteveBrush Blackbaud-SteveBrush force-pushed the date-range-service-no-resolve-resources branch from fdb4985 to 39be5c6 Compare July 22, 2024 18:56
@Blackbaud-SteveBrush Blackbaud-SteveBrush changed the title fix(components/datetime)!: resources strings for default calculators are no resolved in the service fix(components/datetime): resources strings for default calculators are not resolved in the service Jul 22, 2024
@blackbaud-sky-build-user
Copy link
Collaborator

@Blackbaud-SteveBrush Blackbaud-SteveBrush marked this pull request as ready for review July 22, 2024 19:19
@Blackbaud-SteveBrush Blackbaud-SteveBrush merged commit 9ac8cd1 into main Jul 23, 2024
42 checks passed
@Blackbaud-SteveBrush Blackbaud-SteveBrush deleted the date-range-service-no-resolve-resources branch July 23, 2024 13:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
risk level (author): 3 This change has a moderate chance of introducing a bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants