#Entity Field API

I mostly agree with #33 but it would be good to link to the right issue to track the need for managing/customising indexes. The problem here is still valid it's just the solution is not really the right place.

I had a look and ✨ Field type modules cannot maintain their field schema (field type schema change C(R)UD is needed) Needs work or 🐛 Adding an index to an entity's schema is not detected as a change in onEntityTypeUpdate Active are both pretty close. Happy for someone else to close this out, but also leaving opening for now in case this triggers a memory of any more potential duplicates.

I'm not so sure. I don't think the entity schema is an API, which having an alter hook for would kind of imply that. Entity types own their schema and they can alter it through the storage schema handler.

You can't add something to the schema and expect it to work, you'd still need an update function to apply it. We need something to manage indexes better, but I think that should be on the field storage/type definition level.

Won't fix IMHO.

This is still relevant and not implemented yet :)

This is still needed.

Thank you for creating this issue to improve Drupal.

We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

Thank you for creating this issue to improve Drupal.

We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

Thank you for creating this issue to improve Drupal.

We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!