Skip to content

Conversation

Sotatek-Patrick-Vu
Copy link
Collaborator

No description provided.

* @returns {Promise<Operation<any>>} A promise to the long-running operation
*/
async resolve(oobi: string, alias?: string): Promise<any> {
async resolve(oobi: string, alias?: string): Promise<Operation<any>> {
Copy link

Choose a reason for hiding this comment

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

Why any?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I used any to avoid some syntax errors in current tests.
Do you think we should using unknown instead?

Copy link

Choose a reason for hiding this comment

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

I think lets do unknown for now and we can later get more specific operation response types

Copy link

@iFergal iFergal Sep 2, 2025

Choose a reason for hiding this comment

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

Same for other places where we have any

* @returns {Promise<Operation<any>>} A promise to the result
*/
async responded(source: string, said: string): Promise<Response> {
async responded(source: string, said: string): Promise<Operation<any>> {
Copy link

Choose a reason for hiding this comment

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

why any?

Copy link

Choose a reason for hiding this comment

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

Actually, not sure if we needed to change this file - otherwise we are changing the API

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