ft3.template.pkg.obj module¶
Template objects.
- class Pet(class_as_dict: dict[str | string[StringType], Any] | None = None, /, **kwargs: Any)¶
Bases:
ObjectPet of a pet.
- id_: Field[str]¶
Unique identifier for the [sub] pet.
Fields called ‘id’ (including underscore variations) are special, they will automatically be combined with their class name to form a clear object id.
In thise case:
petId.
- enumerations: lib.t.ClassVar[dict[str, tuple[typ.Primitive, ...]]] = {'in_': ('inside', 'outside', 'timeout'), 'type_': ('cat', 'dog')}¶
- fields: lib.t.ClassVar[typ.FieldsTuple] = ('id_', 'in_', 'is_tail_wagging', 'name', 'pet_with_pet_id', 'type_')¶
- hash_fields: lib.t.ClassVar[typ.FieldsTuple] = ('id_', 'pet_with_pet_id')¶
- class PetWithPet(class_as_dict: dict[str | string[StringType], Any] | None = None, /, **kwargs: Any)¶
Bases:
ObjectA simple pet that makes for a good example.
This python docstring will be parsed as the default description for its corresponding RESTful resource.
It will always be parsed as the description / docstring for the Pet object itself in all auto-generated documentation.
It will be rendered in markdown.
- id_: Field[str]¶
Unique identifier for the pet.
Fields called ‘id’ (including underscore variations) are special, they will automatically be combined with their class name to form a clear object id.
In this case:
petWithPetId.
- enumerations: lib.t.ClassVar[dict[str, tuple[typ.Primitive, ...]]] = {'in_': ('inside', 'outside', 'timeout'), 'type_': ('cat', 'dog')}¶
- fields: lib.t.ClassVar[typ.FieldsTuple] = ('human', 'id_', 'in_', 'is_tail_wagging', 'name', 'pets', 'type_')¶
- hash_fields: lib.t.ClassVar[typ.FieldsTuple] = ('id_',)¶