Reactivity is lost when resources are created or received over socket and the resource was not fetched by a list request

[richard-cox]

Setup

• Rancher version: dev of 2.10.0

Describe the bug

• reactive was applied to objects that made it into the store via loadAll or loadPage
• objects that are assigned to a component data object should also be reactive
• however there are scenarios where changes to existing or new properties on these object did not trigger reactivity (computed, watch, etc), specifically when the resource has not been added to the store by loadAll/loadPage
  • A request to create a resource
  • A new resource is received over socket
  • A collection is fetched via labelSelect

To Reproduce

1. Nav to any config maps detail page
2. Update shell/detail/configmap.vue with

    data() {
      return { myObj: null };
    },
   
    async fetch() {
      await this.$store.dispatch('cluster/findAll', { type: 'configmap' });
   
      const myObj = await this.$store.dispatch('cluster/create', {
        type:     'configmap',
        metadata: {
          description: '1111',
          namespace:   'default',
          name:        'myobj',
        }
      });
   
      this.myObj = await myObj.save();
    },
   
    watch: {
      myObj: {
        handler(neu) {
          console.warn('rrc', 'watch', 'myObj', neu);
        },
        deep: true
      }
    },
   

   • on save this will create a new resource default/myobj
3. In another browser do either of below
   • Edit as yaml and add immutable: false
   • Edit config and change the description
4. With the change the console.warn should trigger. without the change it won't

Result

• the console.warn does not trigger

Expected Result

• the console.warn should trigger