IBX-10471: [Inputs] Inputs Validators Base

[GrabowskiM]

🎫 Issue	IBX-10471

Description:

For QA:

Documentation:

[Copilot]

Pull Request Overview

This PR introduces a validation system for input components with a base validator architecture. It establishes the foundation for validating user inputs with support for internationalization through translators.

• Implements a BaseValidator abstract class that serves as the foundation for all validators
• Creates a ValidatorManager to orchestrate multiple validators and collect validation results
• Provides a React hook for easy integration of the validation system in components
• Includes an example IsEmptyStringValidator for string validation

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 3 comments.

File	Description
BaseValidator.ts	Abstract base class defining the validator interface with translator support
ValidatorManager.ts	Manager class that handles multiple validators and aggregates validation results
IsEmptyStringValidator.ts	Concrete validator implementation for checking empty strings
useValidatorManager.ts	React hook for creating and managing validator instances

[Copilot]

Using the definite assignment assertion (!) on _translator without initialization could lead to runtime errors if setTranslator() is not called before accessing the translator. Consider making the translator a required constructor parameter or providing a default value.

Suggested change

	setTranslator(translator: TranslatorType) {
	protected _translator: TranslatorType;
	constructor(translator: TranslatorType) {

[Copilot]

The validate method lacks a return type annotation. Adding ': { isValid: boolean; messages: string[] }' would improve type safety and API clarity.

Suggested change

	validate(value: unknown) {
	validate(value: unknown): { isValid: boolean; messages: string[] } {

[tischsoic]

I think we should avoid naming return types as ...ReturnType because this decreases flexibility. E.g. it may feel strange later to create something like:

const alwaysTrueValidation: ValidateReturnType = {...}

I think we should name it e.g. ValidationResult:

Suggested change

	export interface ValidateReturnType {
	export interface ValidationResult {

[tischsoic]

I guess this is somewhat fine, but it feels wrong to call filter first and then map to collect error messages :D

Suggested change

	.filter((validator: BaseValidator<T>) => !validator.validate(value))
	.map((validator: BaseValidator<T>) => validator.getErrorMessage());
	.reduce((errors , validator) => {
	const isValid = validator.validate(value);
	if (isValid) {
	continue;
	}
	return [...errors, validator.getErrorMessage()];
	}, [])

this is longer but faster to read. :)