All error messages including core at one place

[navalkishoregr]

Why can't we manage all error messages at one place. Suppose we need any custom messages for rest apis and websites combining both is a headache.

[swissspidy]

Can you perhaps elaborate a bit more on which error messages you mean?

Is the problem that you need to write them multiple times for different areas instead of being able to refer to a common error message?

[jnylen0]

There is nothing stopping you from doing this in a plugin. For example:

<?php

function myplugin_get_error( $code ) {
    switch ( $code ) {
        case 'not_allowed':
            return new WP_Error( 'not_allowed', __( 'This operation is not allowed.', 'myplugin' ) );
        case 'not_implemented':
            return new WP_Error( 'not_implemented', __( 'This operation is not implemented yet.', 'myplugin' ) );
    }
}

It's possible that a pattern like this would also be a good fit for parts of core.

[navalkishoregr]

But what is the hook to add this function. Just if we write add this function will we be able to get all errors that are generating.

Replying to jnylen0:

There is nothing stopping you from doing this in a plugin. For example:

<?php

function myplugin_get_error( $code ) {
    switch ( $code ) {
        case 'not_allowed':
            return new WP_Error( 'not_allowed', __( 'This operation is not allowed.', 'myplugin' ) );
        case 'not_implemented':
            return new WP_Error( 'not_implemented', __( 'This operation is not implemented yet.', 'myplugin' ) );
    }
}

It's possible that a pattern like this would also be a good fit for parts of core.

[jnylen0]

This is not something that exists today in WordPress core, and it is unlikely to be worked on soon. I am closing this ticket again, please feel free to leave comments but do not reopen it.

There is nothing stopping you from structuring a plugin or theme this way.