Check DefaultProcessor::handleMissingFields() for infinite loops

[mabar]

Auto-initialization of objects may lead to infinite loops in case of self-references. Needs test for verification.

Metadata-based detection is not possible - even object with all properties required may be still initializable due to before class callback. If no solution is found, feature may be just removed.

Solving it in runtime may not be viable - creating first object in structure and omiting same one deeper in structure is not deterministic behavior.

object-mapper/src/Processing/DefaultProcessor.php

Lines 428 to 442 in 29a0d58

	// Try to initialize object from empty array when no data given
	// Mapped object in compound type is not supported (allOf, anyOf)
	// Used only in default mode - if all or none values are required then we need differentiate whether user sent value or not
	$mappedObjectArgs = $propertyMeta->getRule()->getArgs();
	assert($mappedObjectArgs instanceof MappedObjectArgs);
	try {
	$data[$missingField] = $initializeObjects
	? $this->process([], $mappedObjectArgs->type, $options)
	: $this->processWithoutMapping([], $mappedObjectArgs->type, $options);
	} catch (InvalidData $exception) {
	$type->overwriteInvalidField(
	$missingField,
	InvalidData::create($exception->getType(), Value::none()),
	);
	}

[mabar]

It causes infinite loops. And fork before class callbacks. Unconditional self reference is simply wrong design.

Unconditional self reference should be forbidden during metadata validation.

Both direct and non-direct (A -> B -> C -> A) self references should be validated. But only MappedObjectRule must be inspected, it is the only case where auto-initialization is used.

use Orisai\ObjectMapper\Attributes\Expect\MappedObjectValue;
use Orisai\ObjectMapper\MappedObject;

final class UnconditionalSelfReferenceVO implements MappedObject
{

	/**
	 * @MappedObjectValue(UnconditionalSelfReferenceVO::class)
	 */
	public UnconditionalSelfReferenceVO $self;

}