In laoreet exercitation? Accusantium, pede?
' +\n 'Nascetur, aspernatur pretium feugiat, nullam rerum suscipit pulvinar' +\n 'dignissimos nulla sint, rerum dolorum fames hac.
User has unsaved changes: {{ user.isDirty | yesNo }}
\n\n\n\n```\n\n### Check if tracking is enabled\n\nYou can also check if the model is tracking it’s state using the `noHistory` getter on the instance. Alternatively, you can check if originals have been set using the `hasOriginals` getter.\n\n### Reset the model state\n\nIf a model is dirty, you can reset it to the payload that was passed in the constructor or through the hydrate method. To do this, simply call the `reset` method on the model instance. If there are no originals, then nothing will happen.\n\n### Cloning a model\n\nThough meant to be used internally, feel free to clone the model with the `clone` method on the instance. This will return a fully-qualified clone of the model, however it will not be reactive unless it is set to something that Vuex can observe.\n\n### Model transformations\n\n> **Note:** This feature may change in the future to use only dot-notation (see below), or will at least support it over and above the syntax below. If the current syntax is removed, it will only be removed in a major release.\n\nSometimes, you’ll find yourself in the position where you have a subkey of type `Object` in your model, but you want that subkey’s value to be of type `Number` for the purposes of API compatibility. For example, let’s say you have the following data in a model:\n\n```js\n{\n name: 'Mike',\n email: 'hello@billow.co.za',\n country: {\n id: 1,\n name: 'South Africa'\n }\n}\n```\n\nWhen this payload goes up to your API, you might want to only pass the ID of the country. This is where transformations come in – they allow you to easily grab parts of the model and move them to the root, optionally using a custom key to replace it.\n\nThere are two types of transformations you can make. The first type simply hoists the value you're looking for in a subkey to the root of the model. For example:\n\n```js\nreturn user.transform({\n country: 'id'\n})\n```\n\nThis tells the model to return only the `id` under the `country` key, whilst retaining the key name, yielding:\n\n```js\n{\n name: 'Mike',\n email: 'hello@billow.co.za',\n country: 1\n}\n```\n\nAll well and good, but what if you need to rename the key to `country_id`? This is where the second type of transformation comes in. By passing an array with two parameters that resemble the current and new key names (or an object resembling the current key and the new key pair), we can rename the key easily:\n\n```js\nreturn user.transform({\n country: ['id', 'country_id'] // or\n // country: { id: 'country_id' }\n})\n```\n\nThese both yield:\n\n```js\n{\n name: 'Mike',\n email: 'hello@billow.co.za',\n country_id: 1\n}\n```\n\n#### Hoist by dot-notation\n\nBecause models support dot-notation out of the the box (see the methods below for this), we can further expand on our transformations by hoisting a deeply nested key’s value and optionally renaming it:\n\n```js\nreturn user.transform({ country: 'profile.country.id' })\nreturn user.transform({ country: { 'profile.country.id': 'country_id' } })\n```\n\nThis will yield the same result as before, only we’re now working with a country object inside a the user’s profile.\n\n### Using dot-notation\n\nAs mentioned, models use dot-notation out of the box. With this strategy, we can easily get, pick and omit data from a model.\n\n#### `get`\n\nGet a piece of data from the model, with an optional fallback if the data is falsy.\n\n```html\n{{ user.get('profile.country.name') }}
\n{{ user.get('profile.country.name', 'Unknown') }}
\n```\n\n> **Tip:** Use the `get` filter when you’re not working with a model.\n\n#### `pick`\n\nReturn a limited set of data that your API may require.\n\n```js\nreturn user.pick(['name', 'email'])\n```\n\nYielding:\n\n```js\n{\n name: 'Mike',\n email: 'hello@billow.co.za',\n}\n```\n\n#### `omit`\n\nIn the same vein, omit data that you don’t need:\n\n```js\nreturn user.omit(['profile'])\n```\n\nWhich yields the same thing.\n\n### Conversions\n\nYou can convert a model to string, form-data and JSON-based-form-data using the built-in helper methods:\n\n```js\nreturn user.toString()\nreturn user.toFormData()\nreturn user.toJsonFormData('data')\n```\n\nIn the first case, the model’s enumerable props are simply sent off to `JSON.stringify` and returned.\n\nIn the latter two cases, the first converts the model to a standard `FormData` object, and the second converts it to a type-safe version of `FormData`, where anything that is not a file gets added to a single key in JSON format. Your backend will need to parse this out when parsing compiling the incoming request. For more information, there’s [a nice little article on it](https://blog.rockett.pw/post/dealing-with-formdata) (see the middleware example for Laravel).\n\n## Mutation Helpers\n\n…\n\n## API Client\n\n…\n\n## Passport\n\n…\n\n## Component and Store Factories\n\n…\n\n## Array, Object and String Utilities\n\n…\n","readmeFilename":"readme.md"}