fix: update fields on new speaker member select

[tomrndom]

ref: https://app.clickup.com/t/86b6jhctw

Signed-off-by: Tomás Castillo [email protected]

[Copilot]

Pull request overview

This PR updates the conditional logic for when speaker fields should be replaced with member information during member selection in the speaker form. The fix ensures that for new speakers (entity.id === 0), the fields are always updated when a member is selected, regardless of the global configuration setting.

• Modified conditional logic to handle new speaker member selection
• Ensures member information populates fields for new speakers even when the global replacement setting is disabled

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The conditional logic can be simplified. The current condition checks 'value' twice and calls 'mustReplaceSpeakerFieldsWithMemberInfo()' twice. This can be refactored to: 'value && (mustReplaceSpeakerFieldsWithMemberInfo() || entity.id === 0)' which is more readable and efficient.

Suggested change

	if (
	(value && mustReplaceSpeakerFieldsWithMemberInfo()) ||
	(value && !mustReplaceSpeakerFieldsWithMemberInfo() && entity.id === 0)
	) {
	if (value && (mustReplaceSpeakerFieldsWithMemberInfo() || entity.id === 0)) {

[smarcet]

LGTM