Hi,

JSpecify is going to be the standard way to deal with null safety.
It's already fully implemented in Spring 7 and spring boot 4.

Is there a plan to support JSpecify ?

At the moment I can't find a way to not break the whole chain when using the recommended approach (@NullMarked).
I saw the old post #2643 about null safety but I didn't find any response.

When mapping with default configuration a method public TargetDto toEmbeddedDto(Source entity) (with @NullMarked it's the same as: public @NonNull TargetDto toEmbeddedDto(@NonNull Source entity) the generated code is:

    @Override
    public TargetDto toEmbeddedDto(Source entity) {
        if ( entity == null ) {
            return null; // This break the contract, even it's not possible, the type safety garantes that entity is not null
        }

        RawId id = null;
        
        id = toRawId( entity.getId() );
        TargetDto targetDto = new TargetDto( id );

        return targetDto;
    }

I also try with other configurations like nullValueMappingStrategy = NullValueMappingStrategy.RETURN_DEFAULT but I always pbs:

    @Override
    public TargetDto toEmbeddedDto(Source entity) {

        RawId id = null;
        if ( entity != null ) { // Still not possible but now there is a way to have 
            id = toRawShiftId( entity.getId() );
        }

        TargetDto targetDto = new TargetDto( id );

        return targetDto;
    }

Is there a way with the current implementation to have something like that ?

    @Override
    public TargetDto toEmbeddedDto(Source entity) {

        RawId id = toRawShiftId( entity.getId() );
        TargetDto targetDto = new TargetDto( id );

        return targetDto;
    }