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

fea: use int for ttl #77

Merged
merged 2 commits into from
Jun 17, 2024
Merged

fea: use int for ttl #77

merged 2 commits into from
Jun 17, 2024

Conversation

Dovchik
Copy link
Contributor

@Dovchik Dovchik commented Jun 12, 2024

No description provided.

@Dovchik Dovchik requested a review from asein-sinch June 13, 2024 10:06
return null;
}

public override void Write(Utf8JsonWriter writer, int? value, JsonSerializerOptions options)

Choose a reason for hiding this comment

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

Can you also add a test for this one, in order to cover the case where the TTL is null (the e2e only covers the nominal case)? And maybe check if the value is in the correct range.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

ttl null is checked in tests above as well, WithJson matcher makes a deep equal comparison, so if ttl is present, there will be an error. And any extended validation for other fields then obvious missing id is not supported by sdk

Choose a reason for hiding this comment

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

Let's keep it this way then

@Dovchik Dovchik merged commit 2f93d1b into main Jun 17, 2024
3 checks passed
@Dovchik Dovchik deleted the feat/manage-ttl-as-int branch June 17, 2024 10:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants