Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #62643, comment 12


Ignore:
Timestamp:
11/01/2025 10:53:00 PM (2 months ago)
Author:
grapestain
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #62643, comment 12

    initial v1  
    1 I still think it would be good to change best-practice recommendations to wrapper functions with suitable `try catch` blocks wrapping the print functions, however combining them with the `__` function would I think result in a function count explosion, as there is already `__`, `_x` for context, `_e` for echo, `_n` for pluralisation, combination of these, e.g. `_ex`, `_nx`, than there are combinations with `esc_attr` and `esc_html`, also there are versions suffixed with `_noop`.
     1I still think it would be good to change best-practice recommendations to wrapper functions with suitable `try catch` blocks wrapping the print functions, however combining them with the `__` function would I think result in a function count explosion, as there is already `__`, `_x` for context, `_e` for echo, `_n` for pluralisation, combination of these, e.g. `_ex`, `_nx`, than there are combinations with `esc_attr` and `esc_html` prefixes, also there are versions suffixed with `_noop`.
    22
    33Making ones combined with `sprintf` and `printf` would multiply their numbers (even if the `printf` and the `e` (echo) variants could be covered by the same), whereas some combinations are already missing from the full set (e.g. there is no `esc_attr_ex` and `esc_html_ex`...), so I guess more combinations could create even more "gaps", if we already have missing combos.