Responses to ->getSetting() ignore requested setting string, static return value.

Thanks for the patch!

I don't think the change in the return value is a problem -- it's a bug that it's not returning something in the right format for those settings.

Just one small tweak needed.

Thanks for the prompt review! Fixed that syntax in the branch.

I can't actually see my computed reverse entity reference field available as a block to layout builder! Is there an additional step needed to make it show?

I've made a few more tweaks to your branch.

I can't see a block for the computed field, but I can reproduce the problem and see the fix, so committed the branch.

Thanks!

Ah hell, that's bad reporting on my part. I was using it in a display mode that was being used as a rendered entity.

Maybe I'll make it up to you by figuring out how to get computed fields to show up in the field list in layout builder ;)

Thanks for the persistence and prompt review/help!

> Maybe I'll make it up to you by figuring out how to get computed fields to show up in the field list in layout builder ;)

Beat you to it! It was 🐛 config computed fields aren't listed in the field map Fixed :)

However, I'm going to reopen this as the fix needs to more comprehensively work for all plugin types, and there's a way to do it using the defaults that field types provide. I'm currently working on it.

Ah, I'd already filed 🐛 use $field_type_manager->getDefaultFieldSettings() in ComputedFieldBase::getFieldDefinitionSetting() Fixed to cover the more general case.

Automatically closed - issue fixed for 2 weeks with no activity.