Unexpected Behavior with Nested Refs in Computed Properties

[Scover-w]

const myComp = computed(() => uRefRef.value? uRefRef.value.myRef : "Nop");

When using a ref that contains another ref (nested refs) inside a computed property, the expected reactivity behavior seems inconsistent. Specifically, unwrapping the inner ref does not require .value. This lead to a weird syntax where the first ref need .value and the second one don't. Futhermore, vscode create an error when myRef is used as a :key (it's written that it receive either a Ref|string), indicating that it does not understand that It is automatically unwrapped.

It is a bug that comes from the vue vs code plugin or vue ?

Vue Playground Exemple

useRef.js :

import { ref } from 'vue'

export function useRef(content)
{
    const myRef = ref(content);


    return { myRef }
};

App.vue :

<script setup>
import { ref, watch, computed } from 'vue'
import { useRef } from './useRef';


let uRefRef = ref(useRef("Coucou"));
//let uRefRef = ref(null);

const myComp = computed(() => uRefRef.value? uRefRef.value.myRef : "Nop");

function onClick()
{
  uRefRef.value.myRef.value += "A";
}

</script>

<template>
  <button @click="onClick">Change Val Ref</button>

  <p>-> {{ myComp }}<-</p>
</template>