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

Accept undefined in setLastTxnTs input but treat it as a no-op. This resolves typescript compilation errors while maintaining current behavior #200

Merged
merged 2 commits into from
Aug 29, 2023

Conversation

cleve-fauna
Copy link
Contributor

@cleve-fauna cleve-fauna commented Aug 29, 2023

Ticket(s): #199

Problem

We are producing invalid client.d.ts files as the getter outputs different types for the setter for the field lastTxnTs.

Solution

Accept the same types for input to the lastTxnTs setter as are output from the getter. Maintain current behavior of the setter by ignoring undefined inputs (so users cannot break read their own write by passing in undefined here).

Result

No more typescript errors.

Testing

Running regression tests via GitHub.


By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

…resolves typescript compilation errors while maintaining current behavior
@cleve-fauna cleve-fauna enabled auto-merge (squash) August 29, 2023 15:31
@cleve-fauna cleve-fauna merged commit c302db9 into main Aug 29, 2023
5 checks passed
@cleve-fauna cleve-fauna deleted the main_tsError branch August 29, 2023 15:33
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.

2 participants