Live demo

Documentation

# install dependencies
npm install

# start playground
npm start

Vue 2

npm install --save vrf

import Vue from 'vue'
import Vrf from 'vrf'

Vue.use(Vrf)

Vue 3 (experimental build)

npm install --save vrf@next

import {createApp} from 'vue'
import Vrf from 'vrf'

createApp(...)
  .use(Vrf)
  .mount(...)

• What is vrf?
• Ideology
• What does it look like?
• Basics
  • Object binding
  • Access to the resource
  • Where is the resource?
  • Expressions
  • Sources
  • Groups
  • Scopes
  • Nested entities
  • Autoforms
  • Data loading control
  • Actions
    • Run actions programmatically
  • Default props
  • v-model
• Advanced
  • Architecture
  • Effects API
  • Autocomplete API
  • Adapter API

Vrf (Vue Resource Form) is a solution for quickly writing declarative user interface forms.

First of all vrf is the specification of form components. There are so many great ui frameworks with different components API, so if you want migrate from one to other you will must refactor each form and probably, it isn't what you want. Vrf provides common abstract standard for forms like pure html forms, but more powerful.

This package contains a set of descriptors for each form element that you can use to create your own implementation. If you need to add a new property/feature to some component - this is probably an occasion to think about whether it is possible to add it to the core (this can be discussed in issues). If the it can be added to the core, this will mean that it is included in the standard and all authors of other implementations will also be able to implement it. If this is not possible, the property is added only for the adapter component and will work only for this adapter.

Vrf doesn't depends on current I18n, validation and network interaction libraries. Instead, it provides interfaces for integration with any one.

Vrf 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 autoforming capabilities and not 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.

In other words, the complex things have the right to be complex, but simple must remain simple.

It allows you to write forms in this way:

<rf-form name="User" auto>
  <rf-input name="firstName" />
  <rf-input name="lastName" />
  <rf-switch name="blocked" />
  <rf-select name="roleId" options="roles" />
  <rf-textarea name="comment" />
  <rf-submit>Save</rf-submit>
</rf-form>

Such form will load and save data without a single line of Javascript code. This is possible due to the use of the effects, which describes the general logic of working with entities in your project. If some form required very specific logic, the form can be used in a lower level mode(without "auto" flag).

• expressive syntax
• ease of separation
• I18n
• Validations(as interface)
• autoforms
• nested entities
• option disabled / readonly for entire form
• vuex integration
• unlimited extension using Effects API

Binding to an object is the cornerstone of vrf. This concept assumes that instead of defining a v-model for a field each time, you do a binding once — entirely on the form object, and simply inform each component of the form what the name of the field to which it is attached is called. Due to this knowledge, the form can take on the tasks of internationalization and display of validations (whereas when determining the v-model for each field, you are forced to do it yourself).

<template>

<rf-form v-model="resource" :errors="errors">
  <rf-input name="title">
</rf-form>

</template>

<script>

export default {
  data(){
    return {
       resource: {
          title: ""
       },
       errors:{
         title: ['Should not be empty']
       }
    }
  }
}


</script>

The form passes a reactive context to all child components (using the Provide / Inject API), so any descendant of the form (not even direct) can receive this data. This allows you to break complex forms into parts, but without the need, it is better not to use this opportunity and try to keep the entire form in one file.

There are several ways to access the resource:

• use rf-resource component

<rf-resource v-slot="{$resource}">
  <div>{{$resource}}</div>
</rf-resource>

• use Resource mixin

<template>

<div>
  {{$resource}}
</div>

</template>

<script>

import {Resource} from 'vrf'

export default {
   mixins: [
    Resource
   ]
}

</script>

• implement your own component using accessible descriptors

<template>
<div>
  <input v-model="$value" />
  {{$resource}}
</div>
</template>

<script>

import {descriptors} from 'vrf'

export default {
  extends: descriptors.input
}

</script>

The resource can be in three places:

• in the state of the parent component for the form
• in the state of form(this happens in autoforms, or for example if you do not pass a resource prop). In this case, you can get a reference to the resource using :resource.sync prop.
• in vuex

The standard way of writing expressions that depdends on resource is using $resource variable from scoped slot on rf-form in main form file

<rf-form
  name="Todo"
  v-slot="{$resource}"
>
  <rf-input name="title" :disabled="$resource.id" />
</rf-form>

It won't fail if $resource is not loaded yet, because scoped slot is rendered only after $resource is loaded. All required sources are initialized using empty arrays, so using $sources reference is safe as well.

If your form is splitted into files and you need conditional rendering in the file without rf-form - you should use rf-resource component to access the resource.

Some components (for example, such as selects) require options for their work. For these purposes, the form sources property serves. It expects a hash of all the necessary options that can be accessed in specific components by name.

<template>

<rf-form v-model="resource" :sources="sources">
  <rf-select name="status" options="statuses" />
</rf-form>

</template>

<script>

export default {
  data(){
    return {
      resource: {
        status: 1
      },
      sources: {
        statuses: [
          {
            id: 1,
            title: 'pending'
          },
          {
            id: 2,
            title: 'ready'
          }
        ]
      }
    }
  }
}

</script>

Instead of a string with the name of the options, you may also pass directly an array of options(but it is used less often since vrf's strength is precisely the declarative descriptions of forms and autoforms can load sources by name).

When you use a source name with autoforms, form uses effects to load the collection for a source. Internally, this is achieved by calling the method requireSource on the form when component was mounted or options prop was updated. Then the form chooses the most effective loading strategy depending on the stage at which the method requireSource was called. You may use this method in your own components, when you need sources for their work.

Vrf contains rf-group component that is used for grouping descendants from descriptors.groupItem, like rf-checkbox, rf-radio, or any custom descendant.

Outside of group, groupItem components work like boolean selection:

<template>

<rf-form v-model="resource">
  <rf-checkbox name="isActive" />
</rf-form>
 
</template>

<script>

export default {
  data() {
    return {
      resource: {
        isActive: false
      }
    }
  }
}

</script>

But inside they are used to choose value:

<template>

<rf-form v-model="resource">
  <rf-group name="mode">
    <rf-checkbox name="read" />
    <rf-checkbox name="write" />
  </rf-group>
</rf-form>
 
</template>

<script>

export default {
  data() {
    return {
      resource: {
        mode: 'read'
      }
    }
  }
}

</script>

Choose multiple value:

<template>

<rf-form v-model="resource">
  <rf-group name="modes" multiple>
    <rf-checkbox name="read" />
    <rf-checkbox name="write" />
  </rf-group>
</rf-form>
 
</template>

<script>

export default {
  data() {
    return {
      resource: {
        modes: ['read', 'write']
      }
    }
  }
}

</script>

Also, you can use inverted property on rf-group to invert the behaviour.

Group supports options prop, you can pass an array and use any descendant of descriptors.groupItem as item-component(rf-radio is used by default)

<rf-form v-model="resource">
  <!-- also you  can specify id-key and title-key -->
  <rf-group 
    name="mode" 
    :options="modes"
    item-component="rf-checkbox"
    multiple 
  />
</rf-form>
 
</template>

<script>

export default {
  data() {
    return {
      resource: {
        mode: ['read', 'write']
      },
      modes: [
        {
          id: 'read',
          title: 'Read'
        },
        {
          id: 'write',
          title: 'Write'
        }
      ]
    }
  }
}

</script>

Moreover, sometimes you need to manage some bitwise values in your resource. Groups allow you to manage them. It has two modes - you can use this component as a wrapper for items, or use its options property. It supports inverted mode as well.

<template>

<rf-form v-model="resource">

  <!-- markup mode -->
  <rf-group name="flags" bitwise multiple>
    <!-- value is a power -->
    <rf-checkbox name="visible" value="0" />
    <rf-checkbox name="editable" value="1" />
    <rf-checkbox name="shareable" value="2" />
  </rf-group>

  <!-- rf-bitwise is an alias for rf-group with set bitwise and multiple flags -->
  <rf-bitwise
    name="flags"
    :options="options"
  />
</rf-form>

</template>

<script>

export default {
  data(){
    return {
      resource: {
        flags: 0
      }
    }
  },
  computed: {
    options(){
      return [
        {
          id: 0,
          name: 'visible' // use title instead of name, if you don't need translations
        },
        {
          id: 1,
          name: 'editable'
        },
        {
          id: 2,
          name: 'shareable'
        }
      ]
    }
  }
}


</script>

</template>

There is rf-scope component that helps you to break your form by logical scopes.

For example, if you need to disable only part of form, it'll look like

<rf-form name="User">
  <rf-input name="name" />
  
  <rf-scope :disabled="!isAdmin">
    <rf-checkbox name="readPermission" />
    <rf-checkbox name="writePermission" />
   </rf-scope>
   
   <rf-submit />
</rf-form>

The scope may be submitted separately as a slice of fields which are inside the scope when you use isolated mode

<rf-form name="User">
  <rf-input name="name" />
  
  <rf-scope isolated>
    <rf-input name="token"/>
    
    <rf-submit /> <!-- this submit sends only { token: '...' } object -->
   </rf-scope>
   
   <rf-submit />
</rf-form>

You also can trigger submit if data are changed inside the scope with property autosave

<rf-form name="User">
  <rf-input name="name" />
  
  <rf-scope isolated autosave>
    <rf-switch name="blocked" />
   <rf-scope />
   
   <rf-submit />
</rf-form>

Vrf supports work with nested entities, both single and with collections. To work with them, the rf-nested component is used, which expects a scoped slot with form components for a nested entity. Internally, rf-nested uses the rf-form the required number of times, so the use of rf-nested can be equated with the declaration of the form inside the form, which can be duplicated if necessary.

<template>

<rf-form v-model="resource">
  <rf-input name="title" />
  <rf-nested name="subtasks"> // you may specify translation-name for nested scope, by default it will be singularized name
    <template v-slot="props">
      <rf-input name="title">
      <rf-datepicker name="deadline" />
    </template>
  </rf-nested>
</rf-form>

</template>

<script>

export default {
  data(){
    return {
      resource: {
        title: '',
        subtasks: [
          {
            title: '',
            deadline: new Date
          }
        ]
      }
    }
  }
}


</script>

Autoforms are a special form mode in which the form within itself performs tasks of loading, saving data, forwarding validation errors, and can also perform some side effects, for example, redirecting to a page of a newly created entity.

Autoforms powered by Effects API which allows to create plugins in modular way. Due to this, it is possible to implement the flow of autoforms for the specifics of any project. You may use ready-made effects or implement your own.

Vrf provide some methods on rf-form allows you to manage data loading:

$refs.form.forceReload() // Completely reloading, excplicitly displayed to user

$refs.form.reloadResource() // Reload only resource without showing loaders

$refs.form.reloadResource(['messages']) // Reload only 'messages' key on resource

$refs.form.reloadSources() // Reload only sources

$refs.form.reloadRootResource(['options']) // reload root form resource, useful if nested component affects data on top level

Method reloadResource allows you to write custom components which may reload the piece of data they are responsible for.

import {descriptors} from 'vrf'

export default {
  extends: descriptors.base,
  methods: {
    ... // some logic mutating data on the server
    invalidate(){
      this.$form.reloadResource(this.name)
    }
  }
}

Vrf provides its own way to create simple buttons that activate async requests. These requests are served by effects and the received data stored in the context of the form(by analogy with a resource).

For example, this snippet renders a button that initiates POST request to /archive in a resource context.

<rf-action name="archive" />

You may change requests parameters by props

<rf-action 
  name="archive"
  method="put"
  :data="{force: true}"
  :params="{queryParameter: 1}"
/>

rf-action in adapters may handle pending status by loader showing. Moreover, you can implement your own rf-action view using activator slot

<rf-action name="archive">
  <template v-slot:activator="{on, pending, humanName}">
    <my-great-button v-on="on" :loading="pending">{{humanName}}</my-great-button>
  </template>
</rf-action>

To render the results, in simple cases you can use rf-action-result component(with slot or component).

<rf-action name="loadText" />

<rf-action-result name="loadText" component="some-component-with-data-and-or-status-props" />

<rf-action-result name="loadtext">
  <template v-slot="{data}">
    <p>{{data}}></p>
  </template>
</rf-action-result>

Or/and use event result

<rf-action name="doSomething" @result="onResult" />

If you need reload resource on result, you may use prop reload-on-result

<rf-action name="switchMode" reload-on-result />

If your action must show toast in UI by result, this can be done in the effects. For example, in REST effect $message field will be processed by effect as a message for user and it will be emitted by showMessage.

You may run actions programmatically as well

<template>

<rf-form name="Todo" auto>
  ...
</rf-form>

</template>

<script>
export default {
  methods: {
    attachImage() {
      const data = new FormData()
      this.$form.executeAction('attachImage', {data, method: 'PUT'})
    }
  }
}
</script>

You may specify default props values for some inputs globally during vrf initialization. It allows you to set up common styles for ui framework if it uses props for customization.

Vue.use(Vrf, {
  adapters: [
    VrfVuetify
  ],
  defaultProps: {
    RfInput: {
      outlined: true
    }
  }
})

In some cases you may want to use rf- controls outside of form, if you don't need form functionality, but still want to use the same elements without separating by vrf/non-vrf inputs. Regarding to this vrf inputs support v-model directive, allowing to use them in seamless way

<template>

<div>
  <p>Enter your first name</p>
  <rf-input v-model="firstName" />
</div>

</template>


<script>

export default {
  data(){
    return {
      firstName: ''
    }
  }
}

</script>

Vrf is all about modularity, you may customize almost any part of it. The final result is achieved due to symbiosis of the following components:

• Core(this package) - contains all business logic of forms. It implements form based on standard html components, without any styling and it's the foundation providing APIs for other modules.

• Adapters - implements vrf using some ui framework over link components descriptors from core. Most likely you will use vrf with some adapter.

• Translate lambda - function with (modelProperty, modelName) -> translation signature, used for translations

• Effects - autoforms logic and side effects

• Autocomplete providers - components containing autocompletes logic

Vrf uses effects to deal with auto-forms lifecycle and side effects. There are two types of effects - API and non-API effects.

API effects:

• activated by the auto property of the rf-form
• executed for each event in order of registration in Vue.use(Vrf, {effects: [...]}) until some effect returns promise(this mechanic works only on onLoad, onLoadSources, onLoadSource, onSave, onCreate and onUpdate subscriptions)
• it's possible to choose effect by specify its name in auto property of the rf-form
• by passing EffectExecutor to auto property you may customize autoform logic ad-hoc

non-API effects:

• activated by the effects property of the rf-form
• executed for each event in order of registration
• it's possible to specify effects for current form by passing array of names to the effects property

There are type definitions for more convenient developing effects. If you create a plugin, you should export an effect factory with default options to provide simple way to add new options in the future.

// effect.ts
import {Effect} from 'vrf'

export default (options = {}) : Effect => {
  return{
    name: 'effect-name',
    api: true,
    effect({onLoad, onLoadSource, onLoadSources, onSave, }){
      onLoad((id) => Promise.resolve({}))

      onLoadSource((name) => Promise.resolve([]))

      onLoadSources((names) => Promise.resolve({}))

      onSave((resource) => Promise.resolve())
    }
  }
}


// initialization of vrf in project

import effect from './effect'

const effects = [
  effect()
]

Vue.use(Vrf, {effects})

Effects are mounted after auto/effects props changing and initially after form mounting. There are two effect lifecycle events:

• onMounted - is fired on each effect mounting
• onUnmounted - is fired on each effect unmounting(when managing props are changed or form is destroyed). This subscription should be used to clear some stuff, for example some side event listeners.

There are some subscriptions for api effects:

• onLoad - is fired when form loads the resource
• onLoadSources - is fired when form loads the sources in eager way
• onLoadSource - is fired when form loads only one source because of form.requireSource execution. It happens for example if rf-select appeared as a result of condition rendering
• onSave - is fired when form is submitted. It is optional subscription, instead you may use more convenient onCreate and onUpdate subscriptions.
• onCreate - is fired when form creates new resource
• onUpdate - is fire when form updates new resource
• onCreated - is fired when onCreate returned an id of new created resource. There is a default trap for this event, which reloads form data, but it's possible to override this behaviour by using event.stopPropagation()
• onLoaded - is fired when data is received from backend, the same like after-load-success on the form
• onSuccess - is fired when resource is saved successfully
• onFailure - is fired when resource wasn't saved due to errors

• onValidate - is fired before saving process, stops saving if any listeners returns false

You may implement data convertation after receiving resource from api effect and before sending. For this purpose Effects API has two subscriptions:

• onAfterLoad - is fired each time when vrf received entities from api effect(for resource and for each entity of sources)
• onBeforeSave - is fired before resource will be saved

The listeners of these events are just mappers, which get object and return modified object. It's possible to use many converters in your application, they will be executed in the order of registrations in effects section. Converters should use api: true flag, because they should be executed always when auto is enabled.

There is a standard way to provide user notification customization using onShowMessage subscription. So, you may use showMessage helper to emit message from any effect using type definitions from vrf, and any notifications effect which uses onShowMessage subscription will be able to show this notification.

The component rf-autocomplete is designed to be reusable through providers that contain the logic of fetching/initializing data and any custom functionalities, like special row for creating new resources and so on.

The definition of autocomplete provider is quite similar to an effect definition:

// vrf-search.js
export default () => ({
  name: 'search',
  setup({
    onLoad,
    onMounted,
    onValueChanged
  }) {
    onLoad(async ({query}) => {
      const items = await ...
      
      return items
    })
    
    onMounted(() => {
      // onMounted logic, if you need
    })
    
    onValueChanged(() => {
      // onValueChanged logic, if you need
    })
  }
})

Using as a global plugin

import vrfSearch from './vrf-search'

Vue.use(Vrf, {
  autocompletes: [
    vrfSearch()  
  ]
})

<rf-autocomplete name="title" type="search" title-key="title" />

or ad-hoc

<template>

<rf-autocomplete name="title" :type="search" title-key="title" />

</template>

<script>
import vrfSearch from './vrf-search'

export default {
  computed: {
    search: vrfSearch()
  }
}

</script>

The adapter must export the added components, it can both override components from the vrf, and add new ones(with rf- prefix).

export default {
  name: 'vrf-adapter-name',
  components: {
    RfInput
    ...
  }
}

If you need install hook, you can add it, but you should be aware that it does not receive options, since they refer to vrf. If you want options, you need to export an adapter factory instead of an adapter.

export default (options) => {
  name: 'vrf-adapter-name',
  components: {
    RfInput
    ...
  },
  install(Vue){
  }
}

One of the main things to consider when writing an adapter is that your adapter should not have a dependency vrf or a ui framework that you are wrapping(you must include them only in dev and peer dependencies). Following this rule will avoid duplication of dependencies in the final product. To achieve this, you need set up your bundler to handle vrf as external dependency and import descriptor in usual way.

<template>

<input type="text" v-model="$value" />

</template>

<script>
import {descriptors} from 'vrf'

export default {
  extends: descriptors.input
}

</script>

If you need a basic implementation of element from core - use $vrfParent

<template>

<button @onClick="onClick" v-if="someCondition">{{$label}}</button>
<component :is="$vrfParent" v-else />

</template>

<script>
import {descriptors} from 'vrf'

export default {
  extends: descriptors.action,
  computed: {
    someCondition() {
      ...
    }
  }
}

</script>

After all, add your adapter to vrf

import VrfAdapterName from './vrf-adapter-name'

Vue.use(Vrf, {
  adapters: [
    VrfAdapterName
  ]
})

• vrf-vuetify - adapter for Vuetify.
• vrf-tiny-mce - adapter for Tiny MCE.

• vrf-rest
• vrf-redirect
• vrf-date-converter