forked from cardosofelipe/fast-next-template
fix(forms): handle nullable fields in deepMergeWithDefaults
When default value is null but source has a value (e.g., description field), the merge was discarding the source value because typeof null !== typeof string. Now properly accepts source values for nullable fields. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
@@ -190,6 +190,15 @@ describe('deepMergeWithDefaults', () => {
|
||||
const source = { value: null };
|
||||
expect(deepMergeWithDefaults(defaults, source)).toEqual({ value: null });
|
||||
});
|
||||
|
||||
it('uses source value when default is null but source has value', () => {
|
||||
const defaults = { description: null as string | null, name: '' };
|
||||
const source = { description: 'A real description', name: 'Test' };
|
||||
expect(deepMergeWithDefaults(defaults, source)).toEqual({
|
||||
description: 'A real description',
|
||||
name: 'Test',
|
||||
});
|
||||
});
|
||||
});
|
||||
|
||||
describe('createFormInitializer', () => {
|
||||
|
||||
Reference in New Issue
Block a user