Pulled ALL skills from 15 source repositories: - anthropics/skills: 16 (docs, design, MCP, testing) - obra/superpowers: 14 (TDD, debugging, agents, planning) - coreyhaines31/marketingskills: 25 (marketing, CRO, SEO, growth) - better-auth/skills: 5 (auth patterns) - vercel-labs/agent-skills: 5 (React, design, Vercel) - antfu/skills: 16 (Vue, Vite, Vitest, pnpm, Turborepo) - Plus 13 individual skills from various repos Mosaic Stack is not limited to coding — the Orchestrator and subagents serve coding, business, design, marketing, writing, logistics, analysis, and more. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
3.0 KiB
3.0 KiB
title, impact, impactDescription, type, tags
| title | impact | impactDescription | type | tags | ||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Refs in Arrays and Collections Require .value | MEDIUM | Refs inside reactive arrays, Maps, or Sets are NOT auto-unwrapped like in reactive objects | capability |
|
Refs in Arrays and Collections Require .value
Impact: MEDIUM - Unlike when a ref is a property of a reactive object, refs inside reactive arrays, Maps, and Sets are NOT automatically unwrapped. You must access them with .value, and forgetting this leads to silent bugs.
Vue only auto-unwraps refs when they are properties of reactive objects. When refs are elements in arrays or values in Maps/Sets, they remain as ref objects and require explicit .value access.
Task Checklist
- Always use
.valuewhen accessing refs stored in reactive arrays - Always use
.valuewhen accessing refs stored in reactive Maps or Sets - Consider storing plain values instead of refs in collections to avoid confusion
- Be aware of this when iterating over arrays containing refs
Incorrect:
import { ref, reactive } from 'vue'
const books = reactive([ref('Vue 3 Guide')])
const counts = reactive(new Map([['clicks', ref(0)]]))
// WRONG: Refs in arrays are NOT unwrapped
console.log(books[0]) // Ref object, not 'Vue 3 Guide'
books[0] = 'New Title' // Replaces the ref, doesn't update it!
// WRONG: Refs in Maps are NOT unwrapped
console.log(counts.get('clicks')) // Ref object, not 0
counts.get('clicks')++ // Does nothing useful
Correct:
import { ref, reactive } from 'vue'
const books = reactive([ref('Vue 3 Guide')])
const counts = reactive(new Map([['clicks', ref(0)]]))
// CORRECT: Use .value for refs in arrays
console.log(books[0].value) // 'Vue 3 Guide'
books[0].value = 'New Title' // Updates the ref's value
// CORRECT: Use .value for refs in Maps
console.log(counts.get('clicks').value) // 0
counts.get('clicks').value++ // Increments to 1
// ALTERNATIVE: Just store plain values in collections (simpler)
const books = reactive(['Vue 3 Guide', 'Vuex Handbook'])
const counts = reactive(new Map([['clicks', 0]]))
// No .value needed - but changes to individual items aren't independently reactive
console.log(books[0]) // 'Vue 3 Guide'
console.log(counts.get('clicks')) // 0
// Mutations still trigger reactivity through the reactive wrapper
books[0] = 'New Title' // Works
counts.set('clicks', counts.get('clicks') + 1) // Works
<template>
<!-- In templates, refs in arrays also need special handling -->
<div v-for="(book, index) in books" :key="index">
<!-- If book is a ref, you'd need: -->
{{ book.value }}
<!-- Or use computed to unwrap them first -->
</div>
</template>