Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

question: Cancel/abort async validation #2148

Closed
TheCelavi opened this issue Jul 1, 2023 · 1 comment
Closed

question: Cancel/abort async validation #2148

TheCelavi opened this issue Jul 1, 2023 · 1 comment
Labels
type: question Questions about the usage of the library.

Comments

@TheCelavi
Copy link

I have tried to find any information on how to cancel validation and/or how to create custom cancelable async validator.

When dealing with canceling, RxJS (observables) are way to go, but since this library does not support observables (which is understandable), support for abort signal should be sufficient enough. Especially if async validator contacts server through network for validation (per example, unique email where check is done while user types e-mail address, with some debouncing).

So, question is:

  • Is abort signal supported? (better yet, am I blind 😄 )
  • If abort signal is not supported, are there any plans to provide support?

Thank you!

@TheCelavi TheCelavi added the type: question Questions about the usage of the library. label Jul 1, 2023
@braaar
Copy link
Member

braaar commented Jan 11, 2024

I'm moving this to the discussion tab, as we are trying to keep the issue count low. Please see this issue for an explanation.

@typestack typestack locked and limited conversation to collaborators Jan 11, 2024
@braaar braaar converted this issue into discussion #2368 Jan 11, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
type: question Questions about the usage of the library.
Development

No branches or pull requests

2 participants