Should hardcoded strings and translations functions flagged? · Issue #30 · WordPress/wporg-code-analysis · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently WordPress.Security.EscapeOutput will flag hardcoded strings and translated string as warnings.
Is that too strict for this context, since we want to focus on the minimum repository standard?
Translated string
<p><?php_e( 'When two markers overlap, the marker with the higher stacking order will be on top. The Default is 0.', 'basic-google-maps-placemarks' ); ?></p>
3 | WARNING | All output should be run through an escaping function(like||esc_html_e() or esc_attr_e()), found '_e'.
|| (WordPress.Security.EscapeOutput.UnsafePrintingFunction)
5 | WARNING | All output should be run through an escaping function(see the
|| Security sections in the WordPress Developer Handbooks), found
||'BGMP_NAME'.
|| (WordPress.Security.EscapeOutput.OutputNotEscaped)
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
Currently
WordPress.Security.EscapeOutput
will flag hardcoded strings and translated string as warnings.Is that too strict for this context, since we want to focus on the minimum repository standard?
Translated string
Hardcoded string
The text was updated successfully, but these errors were encountered: