Question 1

How do I add a custom validation rule in Validator?

Accepted Answer

Extend the Rule class and override the validate method, as shown in the README with the CustomRule example. This allows you to define any logic, such as checking for specific string matches or custom patterns.

Question 2

Validator vs Android's built-in form validation: which is better?

Accepted Answer

Validator offers a more declarative approach with extensive pre-built rules and conditions, reducing boilerplate compared to manual validation. However, it's specifically for TextInputLayout, while built-in methods are more general but require more code.

Question 3

Can I use Validator with Jetpack Compose?

Accepted Answer

No, Validator is designed for traditional Android Views, specifically TextInputLayout. For Jetpack Compose, you'd need to look for other validation libraries or implement custom solutions, as it doesn't support Compose's state management.

Question 4

How to handle validation errors in Validator?

Accepted Answer

Use the listener-based callbacks; onValidateFailed provides a list of error messages that you can display in UI or log, as demonstrated in the example with Toast and Log calls for error handling.

Question 5

Does Validator support async validation, like API calls?

Accepted Answer

Not directly; it focuses on synchronous, client-side validation. For server checks, you'd need to integrate async logic separately, such as using coroutines or callbacks outside the library's validation flow.

Question 6

What's the difference between SINGLE and CONTINUOUS modes?

Accepted Answer

SINGLE mode validates all fields at once when triggered, useful for form submissions, while CONTINUOUS mode provides real-time feedback as the user types, enhancing UX for instant error correction, as illustrated with GIFs in the README.

Validator

What is Validator?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions