Vue option should be defined with a valid type

• VUE_MISMATCHED_TYPE_OF_OPTION
• Error
• Medium
• vue

This rule applies when Vue options are defined with invalid types.

If Vue options are defined with invalid types, their meanings are ignored, and Vue outputs a warning message.
For example, the data option of a Vue component cannot be defined as an object. Instead, a function that returns the object should be used.

Noncompliant Code Example

<script>
export default {
  data: { msg: 'hi' }, // VUE_MISMATCHED_TYPE_OF_OPTION alarm because 'data' option's type of a Vue component should be a function.
  methods() { // VUE_MISMATCHED_TYPE_OF_OPTION alarm because 'methods' option's type should be an object.
    return {
      handleClick() {
        // do something
      }
    };
  }
}
</script>

Compliant Code Example

<script>
export default {
  data() {
    return { msg: 'hi' };
  },
  methods: {
    handleClick() {
      // do something
    }
  }
}
</script>

Version

This rule was introduced in DeepScan 1.15.0-beta.

See

• Lifecycle hooks

• Data options

• DOM options

• Asset options

• Composition options

• Miscellaneous options

• [Vue warn]: The data option should be a function that returns a per-instance value in component definitions.

• [Vue warn]: Invalid value for option methods: expected an Object, but got Function.

• [Vue warn]: props must be strings when using array syntax.

• [Vue warn]: Method foo has an undefined value in the component definition. Did you reference the function correctly?

• [Vue warn]: invalid template option:[object Object]