![\"vrf](\"https://raw.githubusercontent.com/dimailn/vrf/master/static/logo.png\"){kind=logo}
\n \n
![](\"https://github.com/dimailn/vrf/actions/workflows/node.js.yml/badge.svg\"){kind=icon}
\n[](https://coveralls.io/github/dimailn/vrf?branch=master)\n![\"npm\"](\"https://img.shields.io/npm/v/vrf\")
\n\n\nLive demo\n\nDocumentation\n\n\n# Build Setup\n\n``` bash\n# install dependencies\nnpm install\n\n# start playground\nnpm start\n```\n\n# Vrf installation\n\nVue 3\n\n```bash\nnpm install --save vrf\n```\n\n```javascript\nimport {createApp} from 'vue'\nimport Vrf from 'vrf'\n\ncreateApp(...)\n .use(Vrf)\n .mount(...)\n\n```\n\n\nVue 2\n\n```bash\nnpm install --save vrf@0.98.2\n```\n\n```javascript\nimport Vue from 'vue'\nimport Vrf from 'vrf'\n\nVue.use(Vrf)\n\n```\n\n\n# Table of contents\n\n- [What is vrf?](#what-is-vrf)\n- [Ideology](#ideology)\n- [What does it look like?](#what-does-it-look-like)\n- [Basics](#basics)\n - [Object binding](#object-binding)\n - [Access to the resource](#access-to-the-resource)\n - [Where is the resource?](#where-is-the-resource)\n - [Expressions](#expressions)\n - [Sources](#sources)\n - [Groups](#groups)\n - [Scopes](#scopes)\n - [Nested entities](#nested-entities)\n - [Autoforms](#autoforms)\n - [Data loading control](#data-loading-control)\n - [Actions](#actions)\n - [Run actions programmatically](#run-actions-programmatically)\n - [Default props](#default-props)\n - [v-model](#v-model)\n- [Advanced](#advanced)\n - [Architecture](#architecture)\n - [Effects API](#effects-api)\n - [Autocomplete API](#autocomplete-api)\n - [Adapter API](#adapter-api)\n\n\n \n\n# What is vrf?\n\nVrf is an abstraction over\n* UI, because it is a set of components' interfaces that should be implemented in adapters\n* Network, because you operate only with terms of the subject area and business actions in application code, and the implementation is delegated to effects\n* I18n, because you can plug in any i18n library(but vue-i18n is supported from the box)\n* Any other areas related to forms, like validations, notifications and analytics, that should be decoupled into plugins, using Effects API\n\n# Ideology\n\nVrf puts form at the forefront of your application, but at the same time all high-level features are provided unobtrusively and their activation is implemented explicitly. The main thesis of vrf is to stay simple while it is possible. This means, for example, that you can make the most of the built-in auto-forming capabilities without having to write any code, but if one day you need a more complex flow than effects can offer, you can simply turn off the auto mode and manually manipulate the form, while still taking the other advantages that vrf gives.\n\nIn other words, the complex things have the right to be complex, but simple should remain simple.\n\n# What does it look like?\n\nIt allows you to write forms in this way:\n\n```vue\n{{data}}>
\n \nEnter your first name
\n