nuxt-ui-tools-table
Use this skill when building or debugging table usage with nuxt-ui-tools as a package consumer. Covers defineTableSchema, useTable, DataList, granular composition, columns, filters, sorting, offset or
SKILL.mdskills/consumer/table/SKILL.md
GitHubnuxt-ui-tools Table
Use this skill for package-consumer tasks involving:
defineTableSchema(...)tableSource(...)useTable(...)DataListDataListRootand granular rendering parts- table columns
- table filters
- client or remote table setup
- table query-state integration
- cursor infinite loading and no-pagination mode
- tree rows (
table.tree) and theexpansionAPI - summary rows (
table.summary) and the view toggle for phones - first-use empty states (
empty) and record names for assistive technology (rowLabel) - touch targets below the
mdbreakpoint (ui.mobile)
Read This Skill With
skills/consumer/package/SKILL.mdskills/consumer/table/references/overview.md
Then use the focused references:
skills/consumer/table/references/getting-started.mdskills/consumer/table/references/data-modes.mdskills/consumer/table/references/url-state.mdskills/consumer/table/references/schema-surface.mdskills/consumer/table/references/layouts.mdskills/consumer/table/references/pagination.mdskills/consumer/table/references/sorting.mdskills/consumer/table/references/filters.mdskills/consumer/table/references/columns.mdskills/consumer/table/references/selection.mdskills/consumer/table/references/tree.mdskills/consumer/table/references/context.mdskills/consumer/table/references/actions.mdskills/consumer/table/references/slots.mdskills/consumer/table/references/patterns.md
I18n-Friendly Schema Text
Schema-owned table text should be written as translation-friendly lazy values when it comes from app i18n.
Use this pattern for:
- filter labels
- filter placeholders
- preset labels and descriptions
- column labels
- action labels
- static option labels
Example:
const { t } = useI18n()
const schema = defineTableSchema({
tableKey: 'employees',
rowKey: 'id',
filters: {
search: {
fields: ['fullName', 'email'],
placeholder: () => t('employees.search.placeholder'),
},
ui: (filter) => [
filter.text('fullName', {
label: () => t('employees.filters.name'),
editor: {
placeholder: () => t('employees.filters.searchName'),
},
}),
filter.date('hiredAt', {
label: () => t('employees.filters.hiredAt'),
editor: {
scalar: {
presets: [
{
label: () => t('shared.datePresets.today'),
value: ({ now }) => now,
},
],
},
},
}),
],
},
rowActions: ({ row }) => [
{
key: 'copy-email',
label: () => t('employees.actions.copyEmail'),
},
],
table: {
columns: (column) => [
column.field('fullName', {
label: () => t('employees.columns.fullName'),
}),
],
},
})
Prefer translation keys through t(...) over writing bilingual helpers or rebuilding the whole schema in a computed(...).
If a surface only renders package-owned UI text and does not come from your schema, use the package locale/provider layer instead of duplicating those strings in your app schema.