Timeline for WP Coding standards - escaping the inescapable?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 13, 2020 at 5:53 | answer | added | Jacob Peattie | timeline score: 2 | |
| Feb 13, 2020 at 5:35 | review | Close votes | |||
| Feb 28, 2020 at 3:05 | |||||
| Feb 13, 2020 at 5:33 | vote | accept | Bonovski | ||
| Feb 13, 2020 at 5:33 | comment | added | Bonovski | I would think so too, but PHPCS with the latest WP Coding standards is "insisting" on escaping it, that's why I asked. I did, what @Tim Elsass suggested and used wp_kses on both. | |
| Feb 12, 2020 at 14:00 | comment | added | Jacob Peattie |
My opinion is that you wouldn't. wc_price() and $product->get_image() are both escaped further upstream. In the WordPress Coding Standards sniffs for PHPCS, these would be referred to as "auto escaped functions".
|
|
| Feb 12, 2020 at 12:50 | answer | added | Tim Elsass | timeline score: 2 | |
| Feb 12, 2020 at 12:36 | history | asked | Bonovski | CC BY-SA 4.0 |