messages or message which is the route?

would this also fix why there is no route to the message entity?

even drupal console created entities get a canonical link to the entity at: admin/structure/message/[mid]

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

Now we have a view with path: 'admin/content/message' and this path is also specified in the message.routing.yml file

message.messages:
  path: '/admin/content/message'
  defaults:
    _title: 'Messages'
    _entity_list: 'message'
  requirements:
    _permission: 'overview messages'

@balagan,

The view is optional. If the view is not installed, the entity list is displayed. The view overrides the entity list when it is installed.

I am open to removing the route from message.routing.yml.

The problem is, currently the Messages tab under /admin/content doesn't display. As the view is optional, maybe should revert this change and keep the different paths?

The missing message tab is a real issue. I think the EntityList should be removed from message.routing.yml and update message.links.task.yml. Or, maybe the view can be updated to have a tab.

I am opposed to having two paths. It isn't very clear. The view is better than the entity list, both in appearance and because site builders can modify a view.

If you want to retain the entity list and allow the view to override it, and retain the message tab, we can try updating the view to have a tab. Another option is to create a controller for the route. If the view is present display the view, otherwise the entity list.

Removing the message.messages route from the message.routing.yml file and its link from the message.links.yml file solves the problem.
The Message tab displays, linking to the view, and the link from the toolbar dropdown is removed.

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