Possible regression in how events are listed for selection when adding a event to a model

Problem/Motivation

1.0.0-alpha2 changed the way that events are ordered/grouped in the selection list when adding a new event to a model.

In 1.0.0-alpha1 the events were grouped by type, and then alphabetically. So, all of the content events were grouped together, all of the user events together, etc.

In 1.0.0-alpha2 the list of available events is ordered solely alphabetically, so no grouping by type.

I don't know if this change was by design, but my immediate reaction is that the previous sorting was preferable - if you wanted a user based event, you knew that they would all be grouped together. Having them scattered risks missing what you want or not realising that the event is from a specific type.

Steps to reproduce

1. Create a new model
2. Click on the button to add a new event to the model
3. View the list of events available for selection from the dropdown list

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes