{"id":3033,"date":"2017-03-23T12:05:10","date_gmt":"2017-03-23T19:05:10","guid":{"rendered":"https:\/\/www.couchbase.com\/blog\/?p=3033"},"modified":"2023-06-19T03:13:06","modified_gmt":"2023-06-19T10:13:06","slug":"fakeit-series-3-5-lean-models-through-definitions","status":"publish","type":"post","link":"https:\/\/www.couchbase.com\/blog\/pt\/fakeit-series-3-5-lean-models-through-definitions\/","title":{"rendered":"S\u00e9rie FakeIt 3 de 5: Modelos Lean por meio de defini\u00e7\u00f5es"},"content":{"rendered":"

Aaron Benton \u00e9 um arquiteto experiente, especializado em solu\u00e7\u00f5es criativas para desenvolver aplicativos m\u00f3veis inovadores. Ele tem mais de 10 anos de experi\u00eancia em desenvolvimento de pilha completa, incluindo ColdFusion, SQL, NoSQL, JavaScript, HTML e CSS. Atualmente, Aaron \u00e9 Arquiteto de Aplicativos da Shop.com em Greensboro, Carolina do Norte, e \u00e9 um Campe\u00e3o da comunidade do Couchbase<\/a>.<\/p>\n

\"Aaron<\/p>\n

S\u00e9rie FakeIt 3 de 5: Modelos Lean por meio de defini\u00e7\u00f5es<\/strong><\/h2>\n

Em nossa postagem anterior FakeIt S\u00e9rie 2 de 5<\/a>: Dados compartilhados e depend\u00eancias, vimos como criar depend\u00eancias de v\u00e1rios modelos com a FakeIt. Hoje, veremos como podemos criar os mesmos modelos, por\u00e9m menores, aproveitando as defini\u00e7\u00f5es.<\/p>\n

As defini\u00e7\u00f5es s\u00e3o uma forma de criar conjuntos reutiliz\u00e1veis em seu modelo. Elas permitem que voc\u00ea defina um conjunto de propriedades\/valores uma \u00fanica vez, referenciando-os v\u00e1rias vezes em seu modelo. As defini\u00e7\u00f5es em um modelo FakeIt s\u00e3o muito semelhantes ao modo como as defini\u00e7\u00f5es s\u00e3o usadas no Swagger<\/a><\/u>\u00a0\/ Especifica\u00e7\u00e3o de API aberta<\/a><\/u>.<\/p>\n

Modelo de usu\u00e1rios<\/strong><\/h3>\n

Come\u00e7aremos com nosso modelo users.yaml que definimos em nosso primeira publica\u00e7\u00e3o<\/a><\/u>.<\/p>\n

name:\u00a0Users\r\ntype:\u00a0object\r\nkey:\u00a0_id\r\nproperties:\r\n\u00a0 _id:\r\n\u00a0 \u00a0 type:\u00a0string\r\n\u00a0 \u00a0 description:\u00a0The document id built by the prefix \"user_\"\u00a0and the users id\r\n\u00a0 \u00a0 data:\r\n\u00a0 \u00a0 \u00a0 post_build:\u00a0`user_${this.user_id}`\r\n\u00a0 doc_type:\r\n\u00a0 \u00a0 type:\u00a0string\r\n\u00a0 \u00a0 description:\u00a0The document type\r\n\u00a0 \u00a0 data:\r\n\u00a0 \u00a0 \u00a0 value:\u00a0user\r\n\u00a0 user_id:\r\n\u00a0 \u00a0 type:\u00a0integer\r\n\u00a0 \u00a0 description:\u00a0An auto-incrementing number\r\n\u00a0 \u00a0 data:\r\n\u00a0 \u00a0 \u00a0 build:\u00a0document_index\r\n\u00a0 first_name:\r\n\u00a0 \u00a0 type:\u00a0string\r\n\u00a0 \u00a0 description:\u00a0The users first name\r\n\u00a0 \u00a0 data:\r\n\u00a0 \u00a0 \u00a0 build:\u00a0faker.name.firstName()\r\n\u00a0 last_name:\r\n\u00a0 \u00a0 type:\u00a0string\r\n\u00a0 \u00a0 description:\u00a0The users last name\r\n\u00a0 \u00a0 data:\r\n\u00a0 \u00a0 \u00a0 build:\u00a0faker.name.lastName()\r\n\u00a0 username:\r\n\u00a0 \u00a0 type:\u00a0string\r\n\u00a0 \u00a0 description:\u00a0The username\r\n\u00a0 \u00a0 data:\r\n\u00a0 \u00a0 \u00a0 build:\u00a0faker.internet.userName()\r\n\u00a0 password:\r\n\u00a0 \u00a0 type:\u00a0string\r\n\u00a0 \u00a0 description:\u00a0The users password\r\n\u00a0 \u00a0 data:\r\n\u00a0 \u00a0 \u00a0 build:\u00a0faker.internet.password()\r\n\u00a0 email_address:\r\n\u00a0 \u00a0 type:\u00a0string\r\n\u00a0 \u00a0 description:\u00a0The users email address\r\n\u00a0 \u00a0 data:\r\n\u00a0 \u00a0 \u00a0 build:\u00a0faker.internet.email()\r\n\u00a0 created_on:\r\n\u00a0 \u00a0 type:\u00a0integer\r\n\u00a0 \u00a0 description:\u00a0An epoch time of when the user was created\r\n\u00a0 \u00a0 data:\r\n\u00a0 \u00a0 \u00a0 build:\u00a0new Date(faker.date.past()).getTime()<\/pre>\n
Digamos que temos um novo requisito em que precisamos oferecer suporte a um endere\u00e7o residencial e comercial para cada usu\u00e1rio. Com base nesse requisito, decidimos criar uma propriedade de n\u00edvel superior chamada endere\u00e7os que conter\u00e1 propriedades aninhadas de resid\u00eancia e trabalho.<\/p>\n
{\r\n\u00a0 \u00a0...\r\n\u00a0 \u00a0\"addresses\": {\r\n\u00a0 \u00a0 \u00a0 \u00a0\"home\": {\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\"address_1\": \"123 Broadway St\",\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\"address_2\": \"Apt. C\",\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\"locality\": \"Greensboro\",\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\"region\": \"NC\",\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\"postal_code\": \"27409\",\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\"country\": \"US\"\r\n\u00a0 \u00a0 \u00a0 \u00a0},\r\n\u00a0 \u00a0 \u00a0 \u00a0\"work\": {\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\"address_1\": \"321 Morningside Ave\",\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\"address_2\": \"\",\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\"locality\": \"Greensboro\",\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\"region\": \"NC\",\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\"postal_code\": \"27409\",\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\"country\": \"US\"\r\n\u00a0 \u00a0 \u00a0 \u00a0}\r\n\u00a0 \u00a0}\r\n}\r\n\r\n<\/pre>\n
Nosso modelo users.yaml precisar\u00e1 ser atualizado para dar suporte a essas novas propriedades de endere\u00e7o.<\/p>\n
(Para fins de brevidade, as outras propriedades foram deixadas de fora da defini\u00e7\u00e3o do modelo)<\/em><\/p>\n
...\r\nproperties:\r\n\u00a0...\r\n\u00a0 addresses:\r\n\u00a0 \u00a0 type:\u00a0object\r\n\u00a0 \u00a0 description:\u00a0An object containing the home and work addresses for the user\r\n\u00a0 \u00a0 properties:\r\n\u00a0 \u00a0 \u00a0 home:\r\n\u00a0 \u00a0 \u00a0 \u00a0 type:\u00a0object\r\n\u00a0 \u00a0 \u00a0 \u00a0 description:\u00a0The users home address\r\n\u00a0 \u00a0 \u00a0 \u00a0 properties:\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 address_1:\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 type:\u00a0string\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 description:\u00a0The address 1\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 data:\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 build:\u00a0`${faker.address.streetAddress()} ${faker.address.streetSuffix()}`\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 address_2:\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 type:\u00a0string\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 description:\u00a0The address 2\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 data:\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 build:\u00a0chance.bool({ likelihood: 35\u00a0}) ? faker.address.secondaryAddress() : null\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 locality:\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 type:\u00a0string\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 description:\u00a0The city \/ locality\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 data:\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 build:\u00a0faker.address.city()\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 region:\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 type:\u00a0string\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 description:\u00a0The region \/ state \/ province\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 data:\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 build:\u00a0faker.address.stateAbbr()\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 postal_code:\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 type:\u00a0string\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 description:\u00a0The zip code \/ postal code\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 data:\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 build:\u00a0faker.address.zipCode()\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 country:\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 type:\u00a0string\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 description:\u00a0The country code\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 data:\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 build:\u00a0faker.address.countryCode()\r\n\u00a0 \u00a0 \u00a0 work:\r\n\u00a0 \u00a0 \u00a0 \u00a0 type:\u00a0object\r\n\u00a0 \u00a0 \u00a0 \u00a0 description:\u00a0The users home address\r\n\u00a0 \u00a0 \u00a0 \u00a0 properties:\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 address_1:\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 type:\u00a0string\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 description:\u00a0The address 1\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 data:\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 build:\u00a0`${faker.address.streetAddress()} ${faker.address.streetSuffix()}`\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 address_2:\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 type:\u00a0string\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 description:\u00a0The address 2\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 data:\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 build:\u00a0chance.bool({ likelihood: 35\u00a0}) ? faker.address.secondaryAddress() : null\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 locality:\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 type:\u00a0string\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 description:\u00a0The city \/ locality\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 data:\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 build:\u00a0faker.address.city()\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 region:\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 type:\u00a0string\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 description:\u00a0The region \/ state \/ province\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 data:\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 build:\u00a0faker.address.stateAbbr()\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 postal_code:\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 type:\u00a0string\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 description:\u00a0The zip code \/ postal code\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 data:\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 build:\u00a0faker.address.zipCode()\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 country:\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 type:\u00a0string\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 description:\u00a0The country code\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 data:\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 build:\u00a0faker.address.countryCode()<\/pre>\n
Como voc\u00ea pode ver, nossas propriedades de endere\u00e7o residencial e comercial cont\u00eam exatamente as mesmas propriedades aninhadas. Essa duplica\u00e7\u00e3o torna nosso modelo maior e mais detalhado. Al\u00e9m disso, o que acontecer\u00e1 se nossos requisitos de endere\u00e7o precisarem mudar? Ter\u00edamos que fazer duas atualiza\u00e7\u00f5es para manter a mesma estrutura. \u00c9 nesse ponto que podemos tirar proveito das defini\u00e7\u00f5es, definindo uma \u00fanica maneira de criar um endere\u00e7o e fazer refer\u00eancia a ele.<\/p>\n
(Para fins de brevidade, as outras propriedades foram deixadas de fora da defini\u00e7\u00e3o do modelo)<\/em><\/p>\n
...\r\nproperties:\r\n\u00a0...\r\n\u00a0 addresses:\r\n\u00a0 \u00a0 type:\u00a0object\r\n\u00a0 \u00a0 description:\u00a0An object containing the home and work addresses for the user\r\n\u00a0 \u00a0 properties:\r\n\u00a0 \u00a0 \u00a0 home:\r\n\u00a0 \u00a0 \u00a0 \u00a0 description:\u00a0The users home address\r\n\u00a0 \u00a0 \u00a0 \u00a0 schema:\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0$ref: '#\/definitions\/Address'\r\n\u00a0 \u00a0 \u00a0 work:\r\n\u00a0 \u00a0 \u00a0 \u00a0 description:\u00a0The users work address\r\n\u00a0 \u00a0 \u00a0 \u00a0 schema:\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0$ref: '#\/definitions\/Address'\r\ndefinitions:\r\n\u00a0 Address:\r\n\u00a0 \u00a0 type:\u00a0object\r\n\u00a0 \u00a0 properties:\r\n\u00a0 \u00a0 \u00a0 address_1:\r\n\u00a0 \u00a0 \u00a0 \u00a0 type:\u00a0string\r\n\u00a0 \u00a0 \u00a0 \u00a0 description:\u00a0The address 1\r\n\u00a0 \u00a0 \u00a0 \u00a0 data:\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 build:\u00a0`${faker.address.streetAddress()} ${faker.address.streetSuffix()}`\r\n\u00a0 \u00a0 \u00a0 address_2:\r\n\u00a0 \u00a0 \u00a0 \u00a0 type:\u00a0string\r\n\u00a0 \u00a0 \u00a0 \u00a0 description:\u00a0The address 2\r\n\u00a0 \u00a0 \u00a0 \u00a0 data:\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 build:\u00a0chance.bool({ likelihood: 35\u00a0}) ? faker.address.secondaryAddress() : null\r\n\u00a0 \u00a0 \u00a0 locality:\r\n\u00a0 \u00a0 \u00a0 \u00a0 type:\u00a0string\r\n\u00a0 \u00a0 \u00a0 \u00a0 description:\u00a0The city \/ locality\r\n\u00a0 \u00a0 \u00a0 \u00a0 data:\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 build:\u00a0faker.address.city()\r\n\u00a0 \u00a0 \u00a0 region:\r\n\u00a0 \u00a0 \u00a0 \u00a0 type:\u00a0string\r\n\u00a0 \u00a0 \u00a0 \u00a0 description:\u00a0The region \/ state \/ province\r\n\u00a0 \u00a0 \u00a0 \u00a0 data:\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 build:\u00a0faker.address.stateAbbr()\r\n\u00a0 \u00a0 \u00a0 postal_code:\r\n\u00a0 \u00a0 \u00a0 \u00a0 type:\u00a0string\r\n\u00a0 \u00a0 \u00a0 \u00a0 description:\u00a0The zip code \/ postal code\r\n\u00a0 \u00a0 \u00a0 \u00a0 data:\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 build:\u00a0faker.address.zipCode()\r\n\u00a0 \u00a0 \u00a0 country:\r\n\u00a0 \u00a0 \u00a0 \u00a0 type:\u00a0string\r\n\u00a0 \u00a0 \u00a0 \u00a0 description:\u00a0The country code\r\n\u00a0 \u00a0 \u00a0 \u00a0 data:\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 build:\u00a0faker.address.countryCode()<\/pre>\n
As defini\u00e7\u00f5es s\u00e3o definidas na raiz do modelo, especificando uma propriedade definitions: e, em seguida, o nome da defini\u00e7\u00e3o. As defini\u00e7\u00f5es s\u00e3o referenciadas usando $ref com o valor sendo o caminho para a defini\u00e7\u00e3o, por exemplo, #\/definitions\/Address. Com o uso de defini\u00e7\u00f5es, economizamos quase 30 linhas de c\u00f3digo em nosso modelo e criamos um \u00fanico local para a defini\u00e7\u00e3o e a gera\u00e7\u00e3o de um endere\u00e7o em nosso modelo de usu\u00e1rios.<\/p>\n
Podemos testar a sa\u00edda de nossos endere\u00e7os de modelo de usu\u00e1rios atualizados usando o seguinte comando:<\/p>\n
fakeit console --count 1 models\/users.yaml\r\n\r\n<\/pre>\n
\"\"<\/p>\n
Agora, digamos que tenhamos um requisito para armazenar o n\u00famero de telefone principal de um usu\u00e1rio e, em seguida, armazenar n\u00fameros de telefone adicionais opcionais, ou seja, residencial, comercial, celular, fax etc. Para essa altera\u00e7\u00e3o, usaremos duas novas propriedades de n\u00edvel superior: main_phone e additional_phones, que s\u00e3o uma matriz.<\/p>\n
{\r\n\u00a0 \u00a0...\r\n\u00a0 \u00a0\"main_phone\": {\r\n\u00a0 \u00a0 \u00a0 \u00a0\"phone_number\": \"7852322322\",\r\n\u00a0 \u00a0 \u00a0 \u00a0\"extension\": null\r\n\u00a0 \u00a0},\r\n\u00a0 \u00a0\"additional_phones\": [\r\n\u00a0 \u00a0 \u00a0 \u00a0{\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\"phone_number\": \"3368232032\",\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\"extension\": \"3233\",\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\"type\": \"Work\"\r\n\u00a0 \u00a0 \u00a0 \u00a0},\r\n\u00a0 \u00a0 \u00a0 \u00a0{\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\"phone_number\": \"4075922921\",\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\"extension\": null,\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\"type\": \"Mobile\"\r\n\u00a0 \u00a0 \u00a0 \u00a0}\r\n\u00a0 \u00a0]\r\n}\r\n\r\n<\/pre>\n
Embora esse possa n\u00e3o ser o modelo de dados mais pr\u00e1tico, ou como eu pessoalmente teria modelado esses dados, podemos usar esse exemplo novamente para ilustrar como podemos tirar proveito do uso de defini\u00e7\u00f5es em nosso modelo FakeIt.<\/p>\n
(Para fins de brevidade, as outras propriedades foram deixadas de fora da defini\u00e7\u00e3o do modelo)<\/em><\/p>\n
...\r\nproperties:\r\n\u00a0...\r\n\u00a0 main_phone:\r\n\u00a0 \u00a0 description:\u00a0The users main phone number\r\n\u00a0 \u00a0 schema:\r\n\u00a0 \u00a0 \u00a0$ref: '#\/definitions\/Phone'\r\n\u00a0 \u00a0 data:\r\n\u00a0 \u00a0 \u00a0 post_build:\u00a0|\r\n\u00a0 \u00a0 \u00a0 \u00a0delete this.main_phone.type\r\n\u00a0 \u00a0 \u00a0 \u00a0return this.main_phone\r\n\u00a0 additional_phones:\r\n\u00a0 \u00a0 type:\u00a0array\r\n\u00a0 \u00a0 description:\u00a0The users additional phone numbers\r\n\u00a0 \u00a0 items:\r\n\u00a0 \u00a0 \u00a0$ref: '#\/definitions\/Phone'\r\n\u00a0 \u00a0 \u00a0 data:\r\n\u00a0 \u00a0 \u00a0 \u00a0 min:\u00a01\r\n\u00a0 \u00a0 \u00a0 \u00a0 max:\u00a04\r\ndefinitions:\r\n\u00a0 Phone:\r\n\u00a0 \u00a0 type:\u00a0object\r\n\u00a0 \u00a0 properties:\r\n\u00a0 \u00a0 \u00a0 type:\r\n\u00a0 \u00a0 \u00a0 \u00a0 type:\u00a0string\r\n\u00a0 \u00a0 \u00a0 \u00a0 description:\u00a0The phone type\r\n\u00a0 \u00a0 \u00a0 \u00a0 data:\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 build:\u00a0faker.random.arrayElement([ 'Home', 'Work', 'Mobile', 'Other'\u00a0])\r\n\u00a0 \u00a0 \u00a0 phone_number:\r\n\u00a0 \u00a0 \u00a0 \u00a0 type:\u00a0string\r\n\u00a0 \u00a0 \u00a0 \u00a0 description:\u00a0The phone number\r\n\u00a0 \u00a0 \u00a0 \u00a0 data:\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 build:\u00a0faker.phone.phoneNumber().replace(\/[^0-9]+\/g, '')\r\n\u00a0 \u00a0 \u00a0 extension:\r\n\u00a0 \u00a0 \u00a0 \u00a0 type:\u00a0string\r\n\u00a0 \u00a0 \u00a0 \u00a0 description:\u00a0The phone extension\r\n\u00a0 \u00a0 \u00a0 \u00a0 data:\r\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 build:\u00a0chance.bool({ likelihood: 30\u00a0}) ? chance.integer({ min: 1000, max: 9999\u00a0}) : null<\/pre>\n
Para este exemplo, criamos uma defini\u00e7\u00e3o de Phone que cont\u00e9m 3 propriedades: type, phone_number e extension. Voc\u00ea notar\u00e1 que definimos uma fun\u00e7\u00e3o post_build na propriedade main_phone que remove o atributo type. Isso ilustra como as defini\u00e7\u00f5es podem ser usadas em conjunto com uma fun\u00e7\u00e3o de compila\u00e7\u00e3o para manipular o que \u00e9 retornado pela defini\u00e7\u00e3o. A propriedade additional_phones \u00e9 uma matriz de defini\u00e7\u00f5es de telefone que gerar\u00e1 entre 1 e 4 telefones. Podemos testar a sa\u00edda dos n\u00fameros de telefone do nosso modelo Users atualizado usando o seguinte comando:<\/p>\n
fakeit console --count 1 models\/users.yaml\r\n\r\n<\/pre>\n
\"\"<\/p>\n
Conclus\u00e3o<\/strong><\/h3>\n
As defini\u00e7\u00f5es permitem que voc\u00ea simplifique seus modelos FakeIt criando conjuntos reutiliz\u00e1veis de c\u00f3digo para modelos menores e mais eficientes.<\/p>\n
Pr\u00f3ximo<\/strong><\/h4>\n