Problems when upgrading from 2.x to 3.x

Not sure I'm seeing how this is is breaking things?

If an update hook in another module tries to make changes to permissions as part of the same deployment where search_api_exclude_entity is being upgraded, there's no way to ensure that the other hook runs after search_api_exclude_entity has updated the permissions.

That means that the permission change in the other module fails, because the outdated search_api_exclude_entity permissions are still assigned to some roles.

By using an update hook in search_api_exclude_entity, the custom module can declare a dependency on it.

Odd but sure, updated the hook based on our the 3.0.x version.

issue still exist with different error
Exception thrown while performing a schema update. Cannot rename 'taxonomy_term__field_display_name' to 'field_deleted_data_9ae423e048': table 'field_deleted_data_9ae423e048' already exists.

@suryabhi I don't think that those exceptions relate to this module, and I don't see why we would need the change you're suggesting in merge request 21.

I think the appropriate status for this issue is probably "Fixed"

suryabhi → closed merge request !21

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