Custom namespaced instance

The sensibleDefaults and extend features let you customize the library to better fit into your project.

Anyway, they come with a downside: because they mutate the same VueTypes object, applications sharing the same module (ie: importing the same library instance from node_modules) might alter one another the behavior of validators.

For example suppose we have a library core and an application ui both using VueTypes. In core we define a custom default and use it:

// core/types.js
import VueTypes from 'vue-types'

VueTypes.sensibleDefaults = {
  ...VueTypes.sensibleDefaults,
  string: 'hello',
}

// core/component.vue
import VueTypes from './types'

export default {
  props: {
    greeting: VueTypes.string, // default is 'hello'
  },
}

Now, if we import VueTypes in ui, we might expect the default value for VueTypes.string to be an empty string but, depending on how the bundler imports our modules, that might not be the case.

That's because in the core/types.js module we globally mutated the VueTypes object.

// ui/ui-component.js
import VueTypes from 'vue-types'

export default {
  props: {
    greeting: VueTypes.string, // default is ???
  },
}

Introducing `createTypes`

To prevent this issue, VueTypes provides a createTypes function which returns a fresh namespaced object.

import { createTypes } from 'vue-types'

const MyTypes = createTypes()

const MyComponent = {
  props: {
    name: MyTypes.string,
  },
}

The function accepts an optional object argument with sensible defaults. If nothing is provided, then the new object will have the same defaults as the default VueTypes object.

import { createTypes } from 'vue-types'

// namespaced validators without default values
const MyTypes = createTypes({})

const MyComponent = {
  props: {
    name: MyTypes.string, // default is `undefined`
  },
}

Extending a custom namespaced instance

Like the default VueTypes instance, custom namespaced instances can be extended either by the extend method or (in ES6+ environments) with the extend keyword:

This allow you to setup highly customizable custom validators:

// ./src/prop-types.js

import { createTypes } from 'vue-types'

export default createTypes().extend([
  {
    name: 'positive',
    getter: true,
    type: Number,
    validator: (v) => v > 0,
  },
])

// Usage:
// ./src/my-component.vue
import MyTypes from './prop-types'

export default {
  props: {
    name: MyTypes.string,
    score: MyTypes.positive.isRequired,
  },
}

In E6+ and TypeScript environments, ./scr/prop-types.js could be rewritten as:

// ./src/prop-types.js

import { createTypes, toType } from 'vue-types'

export default class MyTypes extends createTypes() {
  static get positive() {
    return toType({
      type: Number,
      validator: (v) => v > 0,
    })
  }
}

Custom namespaced instance ​

Introducing createTypes ​

Extending a custom namespaced instance ​

Custom namespaced instance

Introducing `createTypes`

Extending a custom namespaced instance