no-reserved-keys.md

Pattern: Use of reserved key

Issue: -

Description

This rule prevents to use reserved names to avoid conflicts and unexpected behavior.

<script>
/* ✗ BAD */
export default {
  props: {
    $el: String
  },
  computed: {
    $on: {
      get () {}
    }
  },
  data: {
    _foo: null
  },
  methods: {
    $nextTick () {}
  }
}
</script>

Options

{
  "vue/no-reserved-keys": ["error", {
    "reserved": [],
    "groups": []
  }]
}

• reserved (string[]) ... Array of additional restricted attributes inside groups. Default is empty.
• groups (string[]) ... Array of additional group names to search for duplicates in. Default is empty.

"reserved": ["foo", "foo2"], "groups": ["firebase"]

<script>
/* ✗ BAD */
export default {
  computed: {
    foo () {}
  },
  firebase: {
    foo2 () {}
  }
}
</script>

Further Reading

• eslint-plugin-vue - no-reserved-keys