@nexdom/uimed-vue 2.0.0-beta.24 → 2.0.0-beta.25

package/AGENTS.md

@@ -151,7 +151,7 @@ Use an existing component (e.g. `button`) as the reference, and deliver all of t
 
 1. `src/components/<name>/<name>.vue` (following the pattern in [Code conventions](#code-conventions)), `types.ts` and `__tests__/<name>.test.ts`.
 2. The `U`-prefixed export in `src/components/index.ts`.
-3. A usage guide at `docs/guide/components/<name>.md`, with `<demo>` examples (and a `<playground>` section when the component has configurable props), and an API reference at `docs/api/components/<name>.md` (props, events and slots tables). Both in Portuguese.
+3. A usage guide at `docs/guide/components/<name>.md`, with `<demo>` examples (and a `<playground>` section when the component has configurable props), and an API reference at `docs/api/components/<name>.md` (props, events and slots tables). Both in Portuguese. In a demo's template inside a `.md` file, don't put an attribute with a template literal after one with an arrow function in the same tag: the Markdown type-check (`vue-tsc`) reads the `>` of `=>` as the end of the tag and fails with `TS1003`. Order the attributes so the template literal comes first.
 4. Both pages registered in the sidebar at `docs/.vitepress/config.ts`.
 5. `e2e/components/<name>.spec.ts` covering the guide's interactive examples and a "UI consistency" screenshot check (plus accessible snapshots where relevant). Commit the generated files under `__snapshots__`/`__screenshot__`.
 6. The full CI sequence passing locally.
@@ -173,7 +173,7 @@ Use an existing composable (e.g. `use-toast`) as the reference, and deliver in t
   - A new component/composable must be listed in its guide page (`docs/guide/…`), its API page (`docs/api/…`), both sidebars in `docs/.vitepress/config.ts`, the guide index table (`docs/guide/index.md`) and the API index list (`docs/api/index.md`).
 - Never write CSS or `<style>` blocks, and expose styling to consumers only through props.
 - Adjustments that Vuetify exposes as Sass variables (e.g. a font family or a line height) go in `src/styles/settings.scss`, which `vitePluginUimed()` compiles into Vuetify's stylesheets in the apps. That file only configures variables: still no CSS rules.
-- Don't add spacing to Vuetify components: no padding or margin utility classes (`pa-*`, `pt-6`, `px-4`, `ma-2`, ...) and no spacing props overriding the defaults. Vuetify already applies Material Design 3 spacing, and overriding it breaks what it handles on its own, such as button paddings and the scrollbar of scrollable content. If the default spacing looks wrong, stop and ask instead of adjusting it.
+- Don't add spacing to Vuetify components: no padding or margin utility classes (`pa-*`, `pt-6`, `px-4`, `ma-2`, ...) and no spacing props overriding the defaults. Vuetify already applies Material Design 3 spacing, and overriding it breaks what it handles on its own, such as button paddings and the scrollbar of scrollable content. If the default spacing looks wrong, stop and ask instead of adjusting it. The one accepted layout margin is `mt-auto` on `v-card-actions` (as in `USection`), which pushes the actions to the bottom of a full-height card without setting any spacing value.
 - Prefer a Vuetify component's own props to building its parts by hand (e.g. `title`/`text` on `v-card` instead of `v-card-item` > `v-card-title` > `v-card-text`). A non-spacing utility class is acceptable only when no prop covers the need (e.g. `text-wrap` on a card title), with a comment saying why.
 - Keep components thin: a component wires props, slots and events to Vuetify. Logic beyond that (focus management, queues, DOM lookups, comparisons) goes into an internal composable with its own unit tests.
 - Path aliases: `@/*` → `src/*`, `@e2e/*` → `e2e/*`.

package/dist/components.d.ts

@@ -1289,6 +1289,12 @@ type DataSetItemProps = {
    * @default "primary"
    */
   variant?: SectionVariant;
+  /**
+   * Actions of the record, like "Editar" and "Excluir", displayed at the
+   * bottom of its card, just like on `USection`. When undefined or empty, no
+   * actions area is rendered.
+   */
+  actions?: SectionAction[];
   /**
    * Component id to use on automated tests.
    */
@@ -1316,7 +1322,11 @@ type DataSetItemSlots = {
  * <template>
  *   <u-data-set :items="patients">
  *     <template #default="{ item }">
- *       <u-data-set-item :title="item.name" subtitle="Beneficiário">
+ *       <u-data-set-item
+ *         :title="item.name"
+ *         subtitle="Beneficiário"
+ *         :actions="[{ label: 'Editar', variant: 'secondary', onClick: () => edit(item) }]"
+ *       >
  *         <u-table :headers="['Plano', 'Idade']" :items="[[item.plan, item.age]]" vertical />
  *       </u-data-set-item>
  *     </template>

package/dist/components.js

@@ -2253,6 +2253,10 @@ var data_set_item_default = /* @__PURE__ */ defineComponent({
 			type: String,
 			required: false
 		},
+		actions: {
+			type: Array,
+			required: false
+		},
 		dataTestid: {
 			type: String,
 			required: false
@@ -2266,6 +2270,7 @@ var data_set_item_default = /* @__PURE__ */ defineComponent({
 				title: props.title,
 				subtitle: props.subtitle,
 				variant: props.variant,
+				actions: props.actions,
 				"data-testid": props.dataTestid,
 				"full-height": ""
 			}, {
@@ -2278,6 +2283,7 @@ var data_set_item_default = /* @__PURE__ */ defineComponent({
 				"title",
 				"subtitle",
 				"variant",
+				"actions",
 				"data-testid"
 			]);
 		};

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nexdom/uimed-vue",
-  "version": "2.0.0-beta.24",
+  "version": "2.0.0-beta.25",
   "description": "A ui framework for NEXDOM applications.",
   "keywords": [
     "lib",