[15.0][IMP] template_content_swapper: allow manual editing of the name

[smorita7749]

This change allows users to edit the mapping name manually.
@qrtl QT6819

[AungKoKoLin1997]

Isn't it possible just by changing readonly to False?

[AungKoKoLin1997]

Do you want to add name before inserting content values? Is that the reason?

[smorita7749]

The intent is to preserve a manually entered name even after content_from / content_to are changed.
I reflected the review for Yoshi-san, so please take a look when you have time.

[AungKoKoLin1997]

Instead of adding logic in both create and onchange, I am wondering why can't we keep original approach just by adding readonly=False attribute. The original compute method depends on content_from and content_to. So, user can still change the name after these values are filled. IMO, changing the name when content_from or content_to is make sense and the name should be updated.

[AungKoKoLin1997]

Shouldn't we keep original practice f"{record.content_from or ''} -> {record.content_to or ''}"? Is there any reason to use only content_from?

[smorita7749]

In the original computed version the name was always rebuilt from content_from / content_to, so including content_to made sense.

Now the record is created as soon as content_from (a required field) is filled, and content_to is optional and often not set yet at that point. So I guess there's no need to build the name from content_to here.

[AungKoKoLin1997]

What I am not comfortable is current improvement breaks the original behavior and always forces us to put the manual name. If we don't do it, the name will always show "content_from" only. I understand the name field in the config is not in important role at the moment but I don't want to break existing behavior and forcing a manual name.

[AungKoKoLin1997]

Same as above.
Isn't better to use write method?

[smorita7749]

name is required=True, so a saved record always has a name, and a write override would have nothing to fill. The onchange fills a default in the form while the record's name is still empty before saving.

[smorita7749]

Instead of adding logic in both create and onchange, I am wondering why can't we keep original approach just by adding readonly=False attribute. The original compute method depends on content_from and content_to. So, user can still change the name after these values are filled. IMO, changing the name when content_from or content_to is make sense and the name should be updated.

The editable-computed way would overwrite the name, but that's what we want to avoid. content_from / content_to can hold long text or markup, so a name built from them is often hard to read. So we want to let users set their own clear name, and keep it even when content_from / content_to are changed later. The auto-fill is just a helper to set a default name while it's empty, and once the user sets a name, we keep it. That's why name is a normal field filled in create / onchange instead of a computed one.