The question about hooks

I’ve just started using nuxt-property-decorator (I’m new with vue-property-decorator as well) and I would like to ask how you remember all the hooks. It’s totally unclear (on the first glance) why some class methods are hooks and the other are just methods. For example,

@Component
export default class ErrorLayout extends Vue {
  @Prop({ type: Object, default: null }) readonly error!: NuxtError
  
  test() {
    return 'test'
  }

  layout() {
    return 'empty'
  }
}

Layout is a hook and placed in the root scope while test is a method and placed inside methods. Isn’t it more intuitive to consider all the class’s methods as vue methods and have something like @AtRoot decorator if anything has to be placed on the root level?

[wiktor-obrebski]

maybe all hooks function should be implemented on base Vue class, with empty body and proper typing? by this it should be much less possible to declare some random properties / functions with same names. and in case of migration - TypeScript would warn the user that the properties are in conflict.

[husayt]

Thanks @wiktor-obrebski, indeed we need to sort this out. If anyone has any suggestions, please.