// Content
                org = dom.getValue();
                val = interpolate(org);
                if (org != val) {
                    dom.setValue(val);
                }
                // Attributes
                for (String attr : dom.getAttributeNames()) {
                    org = dom.getAttribute(attr);
                    val = interpolate(org);
                    if (org != val) {

import static eu.maveniverse.domtrip.maven.MavenPomElements.Attributes.COMBINE_APPEND;
import static eu.maveniverse.domtrip.maven.MavenPomElements.Attributes.COMBINE_CHILDREN;
import static eu.maveniverse.domtrip.maven.MavenPomElements.Attributes.COMBINE_MERGE;
import static eu.maveniverse.domtrip.maven.MavenPomElements.Attributes.COMBINE_OVERRIDE;
import static eu.maveniverse.domtrip.maven.MavenPomElements.Attributes.COMBINE_SELF;

  EXPECT_EQ(
      std::string("Invalid FunctionDef given to TF_FunctionImportFunctionDef"),
      std::string(TF_Message(s_)));
}

TEST_F(CApiFunctionTest, Attribute) {
  DefineFunction(func_name_, &func_);

  // Get non existent attribute
  TF_Buffer* attr_buf = TF_NewBuffer();
  TF_FunctionGetAttrValueProto(func_, "foo_attr", attr_buf, s_);
  EXPECT_EQ(TF_INVALID_ARGUMENT, TF_GetCode(s_));

{* ../../docs_src/body_nested_models/tutorial005_py310.py hl[2,8] *}

Es wird getestet, ob der String eine gültige URL ist, und als solche wird er in JSON Schema / OpenAPI dokumentiert.

## Attribute mit Listen von Kindmodellen { #attributes-with-lists-of-submodels }

Sie können Pydantic-Modelle auch als Typen innerhalb von `list`, `set`, usw. verwenden:

{* ../../docs_src/body_nested_models/tutorial006_py310.py hl[18] *}

 * limitations under the License.
 */

package gradlebuild.basics

import org.gradle.api.attributes.Attribute


enum class GradleModuleApiAttribute {
    API,
    IMPLEMENTATION;

    companion object {
        val attribute = Attribute.of(GradleModuleApiAttribute::class.java)
    }

Notez que `Field` est importé directement depuis `pydantic`, et non depuis `fastapi` comme le sont les autres (`Query`, `Path`, `Body`, etc.).

///

## Déclarer les attributs du modèle { #declare-model-attributes }

Vous pouvez ensuite utiliser `Field` avec des attributs de modèle :

{* ../../docs_src/body_fields/tutorial001_an_py310.py hl[11:14] *}

	Devmajor int64 // Major device number (valid for TypeChar or TypeBlock)
	Devminor int64 // Minor device number (valid for TypeChar or TypeBlock)

	// Xattrs stores extended attributes as PAX records under the
	// "SCHILY.xattr." namespace.
	//
	// The following are semantically equivalent:
	//  h.Xattrs[key] = value
	//  h.PAXRecords["SCHILY.xattr."+key] = value
	//

# https://github.com/tensorflow/tensorflow/blob/cd67f4f3723f9165aabedd0171aaadc6290636e5/tensorflow/tensorflow.bzl#L396-L425
# And is usable in the "deps" attribute instead of the "srcs" attribute
# as a workaround for https://github.com/tensorflow/tensorflow/issues/34117
cc_import(
    name = "libtensorflow_framework_import_lib",
    shared_library = select({

 * See the License for the specific language governing permissions and
 * limitations under the License.
 */
package gradlebuild.basics

/**
 * Attribute values for the different types of architecture data.
 * Used with [org.gradle.api.attributes.Category].
 */
object ArchitectureDataType {
    /**
     * JSON containing platforms data. See root settings file for more information.
     */

/// check | Inspired **FastAPI** to

Define extra validations for data types using the "default" value of model attributes. This improves editor support, and it was not available in Pydantic before.