@redi.run/redi-components 0.0.46 → 0.0.47

package/README.md

@@ -2,20 +2,20 @@
 
 # Redi-Components
 
-
 [![Latest Release](https://gitlab.redi.run/redi/redi-components/-/badges/release.svg)](https://gitlab.redi.run/redi/redi-components/-/releases)
 
-
 [![pipeline status](https://gitlab.redi.run/redi/redi-components/badges/main/pipeline.svg)](https://gitlab.redi.run/redi/redi-components/-/commits/main)
 
 Small, reusable UI component library for Redi projects.
 
 Location
+
 - redi/redi-components
 
 This README describes installation, usage, API conventions, development, testing, publishing and contribution guidelines. Replace placeholder examples with concrete component names and props used in this repository.
 
 ## Table of contents
+
 - Quick Install
 - Basic Usage
 - API reference (how to document each component)
@@ -48,33 +48,40 @@ This README describes installation, usage, API conventions, development, testing
 - **refactor**: Enhanced TypeScript interfaces in `types.ts`. `rowKey` is now strictly typed, and `selectedRows` no longer uses `any[]`.
 
 ## Quick Install
+
 Install from npm or local workspace.
 
 npm:
+
 ```bash
 npm install @redi/redi-components
 ```
 
 yarn:
+
 ```bash
 yarn add @redi/redi-components
 ```
 
 pnpm:
+
 ```bash
 pnpm add @redi/redi-components
 ```
 
 Note any peer dependencies (React, Vue, etc.) in package.json and ensure they are installed in the host project:
+
 ```bash
 # example for React
 npm install react react-dom
 ```
 
 ## Basic Usage
+
 Provide short usage examples for supported frameworks. Replace with real component names.
 
 React (ESM):
+
 ```jsx
 import React from 'react';
 import { Button, Card } from '@redi/redi-components';
@@ -93,12 +100,15 @@ function App() {
 ```
 
 TypeScript:
+
 - Types are exported from the package. Example:
+
 ```ts
 import type { ButtonProps } from '@redi/redi-components';
 ```
 
 Vanilla (if UMD build available):
+
 ```html
 <script src="redi-components.umd.js"></script>
 <script>
@@ -108,7 +118,9 @@ Vanilla (if UMD build available):
 ```
 
 ## API Reference (how to document each component)
+
 For each component include:
+
 - Name and purpose
 - Import path
 - Props / attributes (name, type, default, description)
@@ -118,6 +130,7 @@ For each component include:
 - CSS variables / classnames
 
 Template:
+
 ```md
 ### ComponentName
 Description.
@@ -128,13 +141,16 @@ import { ComponentName } from '@redi/redi-components';
 ```
 
 Props:
+
 - propName: type — default — description
 - onEvent: (event) => void — — description
 
 Example:
+
 ```jsx
 <ComponentName propName="value" onEvent={(e) => {}} />
 ```
+
 ```
 
 ## Theming & Styling
@@ -153,13 +169,16 @@ Example (CSS variables):
 ```
 
 ## Accessibility
+
 - Components must follow WCAG standards.
 - Keyboard interactions documented per component.
 - Use semantic HTML elements and ARIA attributes where necessary.
 - Provide examples of screen-reader usage.
 
 ## Development
+
 Recommended project structure:
+
 ```
 /src
   /components
@@ -171,6 +190,7 @@ Recommended project structure:
 ```
 
 Scripts (examples in package.json):
+
 ```json
 {
   "build": "tsc && rollup -c",
@@ -182,11 +202,13 @@ Scripts (examples in package.json):
 ```
 
 Tips:
+
 - Use TypeScript and export types.
 - Use Storybook or a docs site for live component examples.
 - Keep components composable and documented.
 
 ## Testing & CI
+
 - Unit tests: Jest/Vitest + Testing Library for DOM tests.
 - Snapshot tests for API stability.
 - Accessibility tests using axe-core.
@@ -198,25 +220,30 @@ Tips:
   - publish (on tags)
 
 ## Publishing
+
 - Use semantic-release or manual versioning.
 - Build artifacts: ESM, CJS, UMD (optional), and type declarations (.d.ts).
 - Ensure package.json fields: main, module, types, files, sideEffects.
 - Set up CHANGELOG.md and follow Conventional Commits for automation.
 
 ## Contributing
+
 - Fork -> branch -> PR.
 - Follow commit message guidelines (Conventional Commits).
 - Run tests and linters before PR.
 - Include documentation and examples for new components or breaking changes.
 
 ## Changelog & Versioning
+
 - Follow semantic versioning (MAJOR.MINOR.PATCH).
 - Maintain CHANGELOG.md with notable changes per release.
 
 ## License
+
 - Add license file (e.g., MIT) and reference in package.json.
 
 ## Contact / Maintainers
+
 - Provide maintainer names and preferred contact (email or GitHub handles).
 
 ---

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@redi.run/redi-components",
   "description": "This project was created to define the style of the UI and improve the UX in all projects from REDI",
-  "version": "0.0.46",
+  "version": "0.0.47",
   "type": "module",
   "author": {
     "name": "Jonathan Manchego Sosa",