- API 路由统一: 移除 /api/h5/,统一 /api/pms/ 入口 - 二进制改名: api-server -> pms-api(与服务名一致) - nginx: 合并 /api/ + /pms/api/ 为 /api/pms/ - 新增 docs/API.md 接口文档 - 后端: CabinetDetail 增加 rssi/pow_fail/address/soc 等字段 - Redis 管道批量读取仓体实时数据(SOC/电压/电流/功率) - DB: 所有 TIMESTAMP 列改为 DATETIME(修复类型不匹配) - 用户管理: 新增创建时间/修改时间列,状态改用 Switch - 角色管理/用户管理: 操作按钮改为图标 - PC 设备详情: 基本信息补全 RSSI/ICCID/电源/地址 - PC 卡片: 通道统计改用 Lucide 图标,颜色统一 - PC 二维码: canvas 渲染,含编号文字,支持右键下载 - H5: 按 uni-app 规范修正导航(navigateTo 替代 reLaunch) - H5: 详情页加返回导航条 - H5: 扫码支持摄像头(jsQR)+ ?id= 参数 - H5: 底部 tabBar 在所有页面常显 - H5: 首页统计改为 6 项(设备/通道/空闲/充电/充满/故障) - H5: 下拉刷新 / 上拉加载 - 产品首页: 添加业务联系 - 文档: 清理过时文件,补充缺失规范章节
5.6 KiB
5.6 KiB
title, impact, impactDescription, type, tags
| title | impact | impactDescription | type | tags | |||||
|---|---|---|---|---|---|---|---|---|---|
| Use resolveComponent for String Component Names in Render Functions | HIGH | String component names don't work in Vue 3 render functions; causes silent failures or runtime errors | gotcha |
|
Use resolveComponent for String Component Names in Render Functions
Impact: HIGH - In Vue 2, render functions could use string names for globally or locally registered components. In Vue 3, you must either import components directly or use resolveComponent(). Using string names causes components to render as HTML elements or fail silently.
Task Checklist
- Import components directly when possible (preferred)
- Use
resolveComponent()for dynamically registered components - Use
resolveDynamicComponent()for<component :is="">equivalent - Call
resolveComponent()insidesetup()or the render function - Handle the case when component is not found
Incorrect:
import { h } from 'vue'
export default {
render() {
// WRONG: String names don't resolve to components
return h('div', [
h('my-component', { value: 1 }), // Renders <my-component> HTML element!
h('router-link', { to: '/' }, 'Home') // Also fails
])
}
}
Correct (Direct Import - Preferred):
import { h } from 'vue'
import MyComponent from './MyComponent.vue'
import { RouterLink } from 'vue-router'
export default {
render() {
return h('div', [
h(MyComponent, { value: 1 }),
h(RouterLink, { to: '/' }, () => 'Home')
])
}
}
Correct (resolveComponent for Registered Components):
import { h, resolveComponent } from 'vue'
export default {
components: {
MyComponent: () => import('./MyComponent.vue')
},
setup() {
// Resolve inside setup - component context is available
const MyComponent = resolveComponent('MyComponent')
return () => h('div', [
h(MyComponent, { value: 1 })
])
}
}
// Or resolve inside render function
export default {
render() {
const MyComponent = resolveComponent('MyComponent')
const RouterLink = resolveComponent('RouterLink')
return h('div', [
h(MyComponent, { value: 1 }),
h(RouterLink, { to: '/' }, () => 'Home')
])
}
}
When to Use Each Approach
| Approach | Use When |
|---|---|
| Direct Import | Component is known at build time (most common) |
resolveComponent() |
Component is registered globally or locally by name |
resolveComponent() |
Dynamic component selection from registered set |
Handling Missing Components
import { h, resolveComponent } from 'vue'
export default {
setup() {
// resolveComponent returns the component or the string name if not found
const DynamicComponent = resolveComponent('MaybeRegistered')
// Check if resolution succeeded
if (typeof DynamicComponent === 'string') {
console.warn(`Component "${DynamicComponent}" not found`)
}
return () => h(DynamicComponent, { value: 1 })
}
}
Dynamic Component Selection
import { h, resolveComponent, computed } from 'vue'
export default {
props: ['componentName'],
setup(props) {
// For truly dynamic components, resolve in render function
return () => {
const Component = resolveComponent(props.componentName)
return h(Component, { /* props */ })
}
}
}
For the equivalent of <component :is="componentName">, use resolveDynamicComponent:
import { h, resolveDynamicComponent } from 'vue'
export default {
props: ['componentType'],
setup(props) {
return () => {
// Resolves string names, component objects, or built-in elements
const component = resolveDynamicComponent(props.componentType)
return h(component, { /* props */ })
}
}
}
Practical Example: Tab Component
import { h, resolveComponent, ref } from 'vue'
export default {
setup() {
const currentTab = ref('TabA')
const tabs = ['TabA', 'TabB', 'TabC']
return () => h('div', [
// Tab buttons
h('div', { class: 'tabs' },
tabs.map(tab =>
h('button', {
key: tab,
class: { active: currentTab.value === tab },
onClick: () => currentTab.value = tab
}, tab)
)
),
// Dynamic component based on current tab
h(resolveComponent(currentTab.value))
])
}
}
Resolving Built-in Components
For built-in components like <Transition> or <KeepAlive>, import them directly from Vue:
import { h, Transition, KeepAlive, Teleport, Suspense } from 'vue'
export default {
setup() {
return () => h(Transition, { name: 'fade' }, () =>
h('div', 'Content')
)
}
}
Resolving Directives
Similar pattern for custom directives:
import { h, resolveDirective, withDirectives } from 'vue'
export default {
render() {
const vFocus = resolveDirective('focus')
return withDirectives(
h('input', { type: 'text' }),
[[vFocus]]
)
}
}
Migration from Vue 2
// Vue 2 (worked with registered components)
render(h) {
return h('my-component', { props: { value: 1 } })
}
// Vue 3 (must resolve or import)
import { h, resolveComponent } from 'vue'
render() {
const MyComponent = resolveComponent('my-component')
return h(MyComponent, { value: 1 }) // Note: props go directly, not in 'props' key
}