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(client): Fix incorrect schedule spec boundaries #1120

Merged
merged 4 commits into from
May 25, 2023

Conversation

mjameswh
Copy link
Contributor

What changed

Fix incorrect schedule spec boundaries validation on hour and day-of-month fields

Why

@mjameswh mjameswh changed the title fix(client): Fix incorrecrt schedule spec boundaries fix(client): Fix incorrect schedule spec boundaries May 25, 2023
@@ -497,6 +497,7 @@ export class ScheduleClient extends BaseClient {
}

protected rethrowGrpcError(err: unknown, scheduleId: string, fallbackMessage: string): never {
if (err instanceof TypeError) throw err;
Copy link
Member

Choose a reason for hiding this comment

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

Hmm.. wondering if we can catch the type error at a different level.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

We could, but then we would need that extra check in every function that does encodings. Not a big thing, but that's why I put it there.

Copy link
Member

Choose a reason for hiding this comment

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

Just find it a bit out of place here.
I’ll let you make the call.

@mjameswh mjameswh merged commit 68ccb11 into temporalio:main May 25, 2023
23 checks passed
@mjameswh mjameswh deleted the schedule-spec-boundaries branch May 25, 2023 19:36
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.

[Bug] CalendarSpec components not encoded correctly
2 participants