[wp-trac] [WordPress Trac] #49518: Consider adding domain-specific i18N filter hooks

[WordPress Trac]

#49518: Consider adding domain-specific i18N filter hooks
-------------------------------------------------+-------------------------
 Reporter:  geminilabs                           |       Owner:  whyisjake
     Type:  enhancement                          |      Status:  reopened
 Priority:  normal                               |   Milestone:  5.5
Component:  I18N                                 |     Version:  5.3.2
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing needs-dev-   |     Focuses:  coding-
  note 2nd-opinion                               |  standards
-------------------------------------------------+-------------------------
Changes (by knutsp):

 * keywords:  has-patch needs-testing needs-dev-note => has-patch needs-
     testing needs-dev-note 2nd-opinion
 * status:  closed => reopened
 * focuses:   => coding-standards
 * resolution:  fixed =>


Comment:

 Replying to [comment:12 swissspidy]:
 > Do we use dashes in hook names elsewhere? Seems a bit uncommon. Same
 with the concatenation.

 Concatenated (dynamic?) filters and action strings seems to use "_" to
 connect to the variable part, except `manage_edit-${post_type}_columns`,
 where "edit-${post_type}" seems to be a special case inherited from
 `$current_screen`.

 Normal examples: `option_{$option name}`, `pre_update_option_{$option
 name}`, `pre_update_option_{$option name}` and
 `save_post_{$post->post_type}`.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/49518#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform