Skip to content

Conversation

@flopez7
Copy link
Contributor

@flopez7 flopez7 commented Sep 19, 2025

Issue tracking

#3512

Context behind the change

  • Update return types in EscrowUtils, OperatorUtils, TransactionUtils and WorkerUtils to allow null values
  • Improve error handling in all references

How has this been tested?

Deployed fortune locally and checked that the whole fortune flow works

Release plan

Deploy new typescript SDK version

Potential risks; What to monitor; Rollback plan

None

… and WorkerUtils to allow null values

- Improve error handling in all references
@flopez7 flopez7 requested review from dnechay and portuu3 September 19, 2025 15:45
@flopez7 flopez7 self-assigned this Sep 19, 2025
@vercel
Copy link

vercel bot commented Sep 19, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
human-app Ready Ready Preview Comment Sep 26, 2025 7:48am
human-dashboard-frontend Ready Ready Preview Comment Sep 26, 2025 7:48am
staking-dashboard Ready Ready Preview Comment Sep 26, 2025 7:48am
2 Skipped Deployments
Project Deployment Preview Comments Updated (UTC)
faucet-frontend Ignored Ignored Preview Sep 26, 2025 7:48am
faucet-server Ignored Ignored Preview Sep 26, 2025 7:48am

Copy link
Collaborator

@dnechay dnechay left a comment

Choose a reason for hiding this comment

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

lgtm overall, some minor comments

Could you please also export error classes from sdk as mentioned in the issue? It would help to simplify some error checks for SDK consumers

- Remove unused castings for null values
- Export error classes in SDK
Copy link
Collaborator

@dnechay dnechay left a comment

Choose a reason for hiding this comment

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

LGTM codewise
Please add changesets to this PR as per new SDK release flow

I would also recommend to apply next strategy for any SDK-related PR:

  1. Make necessary changes
  2. Go through review cycles
  3. Get an "approval" comment
  4. Generate changesets and docs once all changes approved

This way you won't have to re-generate docs in review cycle + they won't create noise in "change files" view for PR reviewer, wdyt?
Or maybe even generate docs only in release PR?

…ls, EscrowStatus, and various type aliases

- Adjust null handling in SignatureAuthGuard
- Generated new changeset
@flopez7
Copy link
Contributor Author

flopez7 commented Sep 25, 2025

Thanks for the suggestion @dnechay, will apply it. Pushed new changes with changesets

dnechay
dnechay previously approved these changes Sep 25, 2025
Copy link
Collaborator

@dnechay dnechay left a comment

Choose a reason for hiding this comment

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

LGTM

One non-blocking suggestion

@flopez7 flopez7 merged commit 29d7a04 into develop Sep 26, 2025
12 checks passed
@flopez7 flopez7 deleted the fix/sdk/returned-types branch September 26, 2025 14:45
@flopez7 flopez7 mentioned this pull request Sep 26, 2025
6 tasks
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.

3 participants