I recently implemented Pinia Colada 数据获取库 in my team and accumulated quite a bit of experience. I have organized it here for reference, hoping it will help those doing similar work.
Core Concepts
Let's start with the basic implementation:
javascript
import { ref, computed, watch, onMounted } from 'vue'
export default {
setup() {
const count = ref(0)
const doubled = computed(() => count.value * 2)
watch(count, (newVal, oldVal) => {
console.log(`count: ${oldVal} -> ${newVal}`)
})
onMounted(() => { console.log('组件已挂载') })
return { count, doubled }
}
}
This code demonstrates the basic usage. In real projects, you'll also need to consider error handling and edge cases.
In-depth Analysis
Building on this, we can further optimize:
javascript
import { reactive, toRefs, computed } from 'vue'
function useCounter(initial = 0) {
const state = reactive({ count: initial, history: [initial] })
const doubled = computed(() => state.count * 2)
function increment() {
state.count++
state.history.push(state.count)
}
return { ...toRefs(state), doubled, increment }
}
This pattern is very practical in large projects and can significantly reduce maintenance costs.
Implementation Experience
Usage in real projects tends to be more complex:
javascript
import { ref, computed, watch, onMounted } from 'vue'
export default {
setup() {
const count = ref(0)
const doubled = computed(() => count.value * 2)
watch(count, (newVal, oldVal) => {
console.log(`count: ${oldVal} -> ${newVal}`)
})
onMounted(() => { console.log('组件已挂载') })
return { count, doubled }
}
}
This approach improves both testability and scalability of the code.
Tuning Strategy
Here is a complete example:
javascript
import { reactive, toRefs, computed } from 'vue'
function useCounter(initial = 0) {
const state = reactive({ count: initial, history: [initial] })
const doubled = computed(() => state.count * 2)
function increment() {
state.count++
state.history.push(state.count)
}
return { ...toRefs(state), doubled, increment }
}
Pay attention to edge case handling — this is critical in production environments.
Summary
- 团队协作中约定和文档比技术本身更重要
- 关注社区动态,技术方案需要持续迭代
- 不要为了用新技术而用新技术