feat(2meet-data-optimizer): flag new Hot zone registrations as deprecated
- ADR-003 step 4 (core side): TMDO_Schema_Registry::register() raises _doing_it_wrong() the first time each provider registers a zone=hot field in a request (zone omitted defaults to hot). Fields still register, so existing hot data stays readable. - Cold / warm / archive registrations are unaffected. - Test bootstrap's _doing_it_wrong stub now records calls. - Verify: core unit 658 / integration 459, HP 142/49, WC 10/22 green, phpcs clean - PR: PR-038
This commit is contained in:
+1
-1
@@ -231,7 +231,7 @@ if ( ! function_exists( 'esc_sql' ) ) {
|
||||
}
|
||||
}
|
||||
if ( ! function_exists( '_doing_it_wrong' ) ) {
|
||||
function _doing_it_wrong( string $fn, string $msg, string $ver ): void {}
|
||||
function _doing_it_wrong( string $fn, string $msg, string $ver ): void { $GLOBALS['_doing_it_wrong_calls'][] = array( $fn, $msg ); }
|
||||
}
|
||||
if ( ! function_exists( 'get_option' ) ) {
|
||||
function get_option( string $key, $default = false ) { return $GLOBALS['_wp_options'][ $key ] ?? $default; }
|
||||
|
||||
Reference in New Issue
Block a user