Fix nil pointer panic in serializer for nil any-type fields

[doraemonkeys]

• Do only one thing
• Non breaking API changes
• Tested

What did this pull request do?

Fix: #7274

Added a nil check before calling s.Serializer.Scan(). When both s.fieldValue and s.Serializer are nil, the field is now set to its zero value and returns early, preventing the panic.

User Case Description

Problem

When using any type fields, if both s.fieldValue and s.Serializer are nil, the code would directly call s.Serializer.Scan() at line 974, causing a nil pointer panic.

[propel-code-bot]

Gracefully handle any serializer fields when both fieldValue and Serializer are nil

This PR prevents a nil-pointer panic that occurred when persisting models containing any typed fields decorated with gorm:"serializer:json". The panic was triggered in schema/field.go when s.Serializer was nil yet its Scan method was invoked. A short-circuit branch now returns early after resetting the destination field to its zero value. A dedicated regression test demonstrates the fix across create, update, and read paths.

Key Changes

• Added early-return guard in schema/field.go inside the generated field.Set closure: if s.fieldValue == nil && s.Serializer == nil, set the model field to reflect.Zero and exit.
• Introduced TestSerializerWithAnyType in tests/serializer_test.go covering create, update, query for records where Data any is nil and non-nil.

Affected Areas

• schema/field.go
• tests/serializer_test.go

This summary was automatically generated by @propel-code-bot

[jinzhu]

Can you add some tests?

[doraemonkeys]

Can you add some tests?

Hi, thanks for the review! I've added comprehensive test cases for this fix.