drupal_set_message() accepts a $type parameter (string) that may be one of:
The logging system, on the other hand, defines a different set of severities. Per Drupal\Core\Logger\RfcLoggerTrait, these include:
To facilitate such features as automatic logging of messages (see, for example, #2031199: drupal_set_message('whatever', 'error') should be integrated with logging), these should be harmonized.
Both drupal_set_message() and the logging system should use the same values for their 'severity' or 'type' parameters for consistency. Likely this means that:
Of course, drupal_set_message() is also on the path to obliteration altogether, per #2073817: [META] Remove drupal_set_message() and so this debate may be moot once postponed to 8.1.x.
As noted above, it is not yet clear precisely how this should be implemented, if it should be implemented at all. Further discussion about the merits of this change is required.
Postponing to 8.1.x because this is not needed to resolve a bug or issue prior to 8.x release. Implementation #1 above could likely be made without breaking backwards compatibility (by testing $type to determine if it is a string or an RfcLoggerTrait constant), but this is nonetheless an API change that is hardly critical to 8.x. Implementation #2 is clearly beyond the scope of a change at this stage. If this route is deemed advisable
Not yet determined.
Not yet entirely determined, but clearly this would require a change to the drupal_set_message() function to harmonize the 'levels'.
| Issue category | Task, because this is primarily an API change and does not introduce new functionality. |
|---|---|
| Issue priority | Normal and not-critical because it is not necessary for stabilization of core. |
| Prioritized changes | This is not a prioritized change for the beta phase. |
| Disruption | Potentially disruptive for core, contributed and custom modules because of the potential API change. |
Comments
Comment #1
tibbsa commentedComment #17
smustgrave commentedThank 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!
Comment #18
smustgrave commentedWith drupal_set_message long been removed going to make an assumption this can be closed.
If I'm wrong please re-open!