reactive-bulma 3.2.0 → 4.0.1

package/README.md

@@ -31,7 +31,12 @@ Component library based on React, Bulma, Typescript and Rollup
 
 ## Purpose
 
-After studying [an Udemy course about Typescript](https://github.com/NicolasOmar/typescript-practice), I wanted to start a new project to practice my new knowledge in a meaningful tool. Therefore, I started this project to understand how to create a component library and investigate the best ways to maintain and nourish it as any professional-level alternatives.
+After studying [an Udemy course about Typescript](https://github.com/NicolasOmar/typescript-practice), I wanted to start a new project to practice my new knowledge in a meaningful tool. Therefore, I began this project to understand how to create a component library and investigate the best ways to maintain and nourish it as any professional-level alternatives.
+
+Now I have finished (Jan 31th) [the last story](https://github.com/NicolasOmar/reactive-bulma/issues/80) related to my proposed roadmap; I will change the repo's objectives to the following:
+- Check every new issues raised by users who found new bugs (of any kind) or related to new components or feature improvements of the existing ones.
+- Update dependencies every week, creating alongside its related PR, branch, and PR to maintain track of those updates. 
+- Include ReactiveBulma's components as part of my full-stack app [MyPets](https://github.com/NicolasOmar/my-pets), where I now have code that I can get rid of and, in that process, find new opportunities to enhance components' usability.
 
 ## Status
 
@@ -119,15 +124,15 @@ After studying [an Udemy course about Typescript](https://github.com/NicolasOmar
 
 Several quick start options are available:
 
-- Clone the repo: `git clone https://github.com/NicolasOmar/reactive-bulma.git`
+- Clone the repo: `git clone https://github.com/NicolasOmar/reactive-bulma.git`.
 - Install with [npm](https://www.npmjs.com/package/reactive-bulma): `npm install reactive-bulma@latest`
-  - Before cloning this repo, I recommend installing [Node](https://nodejs.org/en/download/) `>=18` to install packages.
+  - Before cloning this repo, I recommend installing [Node](https://nodejs.org/en/download/) `>=20.10.0` to install packages.
 
 ## Folder structure
 
 In case you have cloned the repo, it will show you the following folders:
-- `_templates:` Dedicated to [Hygen](https://www.hygen.io/) configuration and implementation files. Dedicated to create new components from customizable templates
-- `.github:` [Github Actions](https://github.com/features/actions/) files used to run post-merge.commits like unit test coverage collection.
+- `_templates:` Dedicated to [Hygen](https://www.hygen.io/) configuration and implementation files. Dedicated to creating new components from customizable templates.
+- `.github:` [Github Actions](https://github.com/features/actions/) files used to run post-merge. commits like unit test coverage collection.
 - `.husky:` Dedicated to [Husky](https://typicode.github.io/husky/) configuration files.
 - `.storybook:` Dedicated to [Storybook](https://storybook.js.org/) configuration files.
 - `src:`
@@ -135,21 +140,21 @@ In case you have cloned the repo, it will show you the following folders:
     - `atoms` (from `v1.0.0`).
     - `molecules` (from `v2.0.0`).
     - `organisms` (from `v3.0.0`).
-  - `design`: Location of common design tokens (coded on `.mdx` files) which are displayed above components sections in storybook's instance.
+  - `design`: Location of common design tokens (coded on `.mdx` files) displayed above components sections in the storybook's instance.
   - `functions`: Dedicated to parsers and helper functions for repetitive logic.
-  - `interfaces`: Dedicated to interfaces used in components and functions typing.
-  - `types`: Dedicated to Bulma's style type setting (which are part of component's properties).
+  - `interfaces`: Dedicated to components and functions typing interfaces.
+  - `types`: Dedicated to Bulma's style typesetting (part of the component's properties).
 
 ## Documentation
 
 Reactive bulma's documentation, included in this repo in the root directory, is built with [Storybook](https://storybook.js.org/) and publicly hosted on `Netlify` at <https://reactivebulma.netlify.app/>. The docs may also be run locally.
 
 ### Running documentation locally
-- Go to `reactive-bulma` folder (where you cloned the repo before).
+- Go to the `reactive-bulma` folder (where you cloned the repo before).
 - Open a console and run `npm install` to install the Node.js dependencies, including Storybook (the site builder).
 - Run `npm start`.
 - Wait until a new tab opens with url <http://localhost:6006/> in your browser. 
-  - In case you want to initiate it on the background, you can run `npm run start:cli`.
+  - If you want to initiate it in the background, you can run `npm run start:cli.`
 
 Learn more about `Storybook` by reading its [documentation](https://storybook.js.org/docs/react/get-started/install).
 
@@ -163,9 +168,9 @@ const App = () => (
   <Button text="This is a test" />
 );
 ```
-To see all component's variants and its code snippets, go to [Documentation](#documentation) section.
+To see all component variants and code snippets go to the [Documentation](#documentation) section.
 
-In case you want to create a custom component for your forked Reactive Bulma version, the easiest way is by running the creation script I made, which [instructions are here](#how-to-create-a-template-component).
+If you want to create a custom component for your forked Reactive Bulma version, the easiest way is by running the creation script I made, which [instructions are here](#how-to-create-a-template-component).
 
 ### How to create a template component
 
@@ -174,33 +179,38 @@ After some time, I understood that creating component files is a repetitive and
 - Open a console and run `npm run create` in your console.
 - An will assistant will appear asking about how your component will be named. You can answer with text separated with spaces (` `), underscores  (`_`), or hyphens (`-`)
 - Then, the assistant will ask in which folder you want to create it (based on its type following [Atomic Design hierarchy structure](https://atomicdesign.bradfrost.com/chapter-2/))
-- At last, the script should create all base files to reduce time and focus on custom implementation.
+- Finally, the script should create all base files to reduce time and focus on custom implementation.
 
 Learn more about `Hygen` by reading its [documentation](https://www.hygen.io/docs/quick-start).
 
 ### How to update all dependencies
 
-In case you wanted to make your own fork, I recommend you to updated at least weekly using a custom command `npm run update`, which will run the following commands in order:
-- `update:deps`: Using a [npm-check-updates](https://www.npmjs.com/package/npm-check-updates) script, you will be able to choose which dependencies want to update to latest version
-- `update:doctor`: Will run a set of build and test checks in order to assure your update will not break any current build.
-- `update:storybook`: Will update storybook to lastest version (following its recommended command) followed for a build check (similar to update:doctor, but for storybook only)
+In case you want to make your fork, I recommend you to update at least weekly using a custom command `npm run update`, which will run the following commands in order:
+- `update:deps`: Using a [npm-check-updates](https://www.npmjs.com/package/npm-check-updates) script, you will be able to choose which dependencies want to update to the latest version
+- `update:doctor`: Runs build and test checks to ensure your update will not break any current build.
+- `update:storybook`: Updates storybook to the latest version (following its recommended command) followed for a build check (similar to update:doctor, but for Storybook only)
 
 ## Versioning
 
-After investigating [semantic-release documentation](https://semantic-release.gitbook.io/semantic-release/) (reffer to [#3](https://github.com/NicolasOmar/reactive-bulma/issues/3)) and having a problematic implementation, I decided to change version meaning for this project with the following:
-- Major versions (`1.0.0`, `2.0.0` and beyond) will reffer to milestones/version achievement.
-- Minor versions (`1.1.0`, `1.2.0` and so on) will reffer to branch/story completition.
-- Patch versions (`1.0.1`, `1.0.2` and so on) will reffer to bugfixes only.
+After investigating [semantic-release documentation](https://semantic-release.gitbook.io/semantic-release/) (refer to [#3](https://github.com/NicolasOmar/reactive-bulma/issues/3)) and finishing the last version according to the original roadmap, I decided to give the following meaning to project's versions after `v4.0.0`:
+- Major versions (`5.0.0`, `6.0.0` and beyond) will refer to milestones achievement and significant changes on existing components that will need extra attention before the update.
+- Minor versions (`4.1.0`, `4.2.0`, and so on) will refer to new components or modifications of existing ones.
+- Patch versions (`4.0.1`, `4.0.2`, and so on) will refer to bug fixes or weekly dependencies updates.
 
-In case you are interested in check current project's status, you can go to [Roadmap](#roadmap) section.
+To check the current project's status, go to the [Roadmap](#roadmap) section.
 
 ### Branching
 
-Giving the mentioned release logic, `main` is the only static branch, and each developed feature or fix will have an unique branch with its PR and a merge commit following [semantic versioning](https://semver.org/) and [semantic commits](https://github.com/semantic-release/semantic-release#commit-message-format) specifications.
+Given the mentioned release logic, `main` is the only static branch, and each developed feature or fix will have a unique branch with its PR and a merge commit following [semantic versioning](https://semver.org/) and [semantic commits](https://github.com/semantic-release/semantic-release#commit-message-format) specifications.
 
 ## Roadmap
 
-Having in mind the [versioning section](#versioning), repo's status in a glance can be observed in this table.
+After finishing the last story related to `v4.0.0`, ReactiveBulma's current work is now focused on updating its dependencies in a weekly manner, as well as checking every issue or discussion raised by visitors who are interested in improving the project by proposing new ideas in shape of tickets or issues with its related PR.
+
+In case you want actual short-term status, go to the [project board](https://github.com/users/NicolasOmar/projects/3) (powered by `GitHub Projects`).
+
+<details>
+<summary>Here is the status table I used to keep track of the worked milestones/versions.</summary>
 
 | Version | Progress | Open issues | Closed issues
 | :---: | :---: | :---: | :---: |
@@ -209,6 +219,9 @@ Having in mind the [versioning section](#versioning), repo's status in a glance
 | `v3.0.0` | ![v3.0.0, progress][badge-progress-300] | ![v3.0.0, open][badge-issues-open-300] | ![v3.0.0, closed][badge-issues-closed-300] |
 | `v4.0.0` | ![v4.0.0, progress][badge-progress-400] | ![v4.0.0, open][badge-issues-open-400] | ![v4.0.0, closed][badge-issues-closed-400] |
 
+In case you want the detailed list of current and future features, go to the [roadmap document](https://docs.google.com/document/d/1kWX-dDTD-cQUeB_Vbu0K6xRvtHaSA38h76yQnhiCe9U).
+</details>
+
 [badge-progress-100]: https://img.shields.io/github/milestones/progress-percent/nicolasomar/reactive-bulma/1?label=%20&style=flat&color=informational
 [badge-issues-open-100]: https://img.shields.io/github/milestones/issues-open/nicolasomar/reactive-bulma/1?label=%20&style=flat&color=orange
 [badge-issues-closed-100]: https://img.shields.io/github/milestones/issues-closed/nicolasomar/reactive-bulma/1?label=%20&style=flat&color=success
@@ -222,10 +235,6 @@ Having in mind the [versioning section](#versioning), repo's status in a glance
 [badge-issues-open-400]: https://img.shields.io/github/milestones/issues-open/nicolasomar/reactive-bulma/4?label=%20&style=flat&color=orange
 [badge-issues-closed-400]: https://img.shields.io/github/milestones/issues-closed/nicolasomar/reactive-bulma/4?label=%20&style=flat&color=success
 
-In case you want the short-term status, go to the [project board](https://github.com/users/NicolasOmar/projects/3) (powered by `GitHub Projects`).
-
-In case you want the detailed list of current and future features, go to the [roadmap document](https://docs.google.com/document/d/1kWX-dDTD-cQUeB_Vbu0K6xRvtHaSA38h76yQnhiCe9U).
-
 ## Changelog
 
 The [changelog](https://github.com/NicolasOmar/reactive-bulma/blob/main/CHANGELOG.md) (powered by `semantic-release`) is regularly updated to reflect what's changed in each new release.

package/dist/cjs/index.js

@@ -3329,6 +3329,16 @@ const NavBarItem = ({ testId = null, cssClasses = null, style = null, children,
     return (React.createElement("a", { "data-testid": navBarItemTestId, className: navBarItemClasses, style: style !== null && style !== void 0 ? style : undefined, "aria-hidden": 'true', onClick: onClick !== null && onClick !== void 0 ? onClick : undefined }, children));
 };
 
+const TableHeadCell = ({ testId = null, cssClasses = null, style = null, content, onClick = null }) => {
+    const tableHeadCellTestId = testId !== null && testId !== void 0 ? testId : parseTestId({ tag: 'table-head-cell', parsedClasses: cssClasses !== null && cssClasses !== void 0 ? cssClasses : '' });
+    return (React.createElement("th", { "data-testid": tableHeadCellTestId, className: cssClasses !== null && cssClasses !== void 0 ? cssClasses : undefined, style: style !== null && style !== void 0 ? style : undefined, onClick: onClick !== null && onClick !== void 0 ? onClick : undefined }, content));
+};
+
+const TableCell = ({ testId = null, cssClasses = null, style = null, content, onClick = null }) => {
+    const tableCellTestId = testId !== null && testId !== void 0 ? testId : parseTestId({ tag: 'table-cell', parsedClasses: cssClasses !== null && cssClasses !== void 0 ? cssClasses : '' });
+    return (React.createElement("td", { "data-testid": tableCellTestId, className: cssClasses !== null && cssClasses !== void 0 ? cssClasses : undefined, style: style !== null && style !== void 0 ? style : undefined, onClick: onClick !== null && onClick !== void 0 ? onClick : undefined }, content));
+};
+
 const generateKey = (max = 5000, min = 1) => {
     max = Math.floor(max);
     min = Math.ceil(min);
@@ -3833,6 +3843,17 @@ const NavBarDropdown = ({ testId = null, containerTestId = null, cssClasses = nu
         React.createElement("section", { "data-testid": navBarDropdownTestId, className: navBarDropdownClasses, style: style !== null && style !== void 0 ? style : undefined }, items.map(renderDropdownItem))));
 };
 
+const TableRow = ({ testId = null, cssClasses = null, style = null, headCell = null, listOfCells, isSelected = false, onClick = null }) => {
+    const tableRowClasses = parseClasses([
+        isSelected ? 'is-selected' : null,
+        cssClasses
+    ]);
+    const tableRowTestId = testId !== null && testId !== void 0 ? testId : parseTestId({ tag: 'table-row', parsedClasses: tableRowClasses });
+    return (React.createElement("tr", { "data-testid": tableRowTestId, className: tableRowClasses, style: style !== null && style !== void 0 ? style : undefined, onClick: onClick !== null && onClick !== void 0 ? onClick : undefined },
+        headCell ? React.createElement(TableHeadCell, Object.assign({}, headCell)) : null,
+        listOfCells.map(_cellConfig => (React.createElement(TableCell, Object.assign({ key: `table-row-${generateKey()}` }, _cellConfig))))));
+};
+
 const renderFieldLabel = (labelText) => labelText ? (React.createElement("label", { "data-testid": 'test-form-field-label', className: 'label' }, labelText)) : null;
 const renderFieldBody = (inputControlConfig, isGrouped) => {
     if (isGrouped) {
@@ -3979,6 +4000,26 @@ const Card = ({ testId = null, cssClasses = null, style = null, headerText = nul
         }))) : null));
 };
 
+/* eslint-disable react/prop-types */
+const renderTableSection = (sectionName, configData) => (React.createElement("tr", null, configData.map(_ItemConfig => (React.createElement(TableHeadCell, Object.assign({ key: `table-${sectionName}-item-${generateKey()}` }, _ItemConfig))))));
+const Table = ({ testId = null, cssClasses = null, style = null, head, body, foot = null, isBordered = false, isStriped = false, isNarrow = false, isHoverable = false, isFullwidth = false, isContained = false }) => {
+    const tableClasses = parseClasses([
+        'table',
+        isBordered ? 'is-bordered' : null,
+        isStriped ? 'is-striped' : null,
+        isNarrow ? 'is-narrow' : null,
+        isHoverable ? 'is-hoverable' : null,
+        isFullwidth ? 'is-fullwidth' : null,
+        cssClasses
+    ]);
+    const tableTestId = testId !== null && testId !== void 0 ? testId : parseTestId({ tag: 'table', parsedClasses: tableClasses });
+    const TableElement = () => (React.createElement("table", { "data-testid": tableTestId, className: tableClasses, style: style !== null && style !== void 0 ? style : undefined },
+        React.createElement("thead", { "data-testid": `${tableTestId}-head` }, renderTableSection('head', head)),
+        React.createElement("tbody", { "data-testid": `${tableTestId}-body` }, body.map(_bodyRowConfig => (React.createElement(TableRow, Object.assign({ key: `table-body-item-${generateKey()}` }, _bodyRowConfig))))),
+        foot ? (React.createElement("tfoot", { "data-testid": `${tableTestId}-foot` }, renderTableSection('foot', foot))) : null));
+    return isContained ? (React.createElement("section", { "data-testid": `${tableTestId}-container`, className: 'table-container' }, React.createElement(TableElement, null))) : (React.createElement(TableElement, null));
+};
+
 exports.Block = Block;
 exports.Box = Box;
 exports.BreadcrumbItem = BreadcrumbItem;
@@ -4025,6 +4066,10 @@ exports.RadioButton = RadioButton;
 exports.Section = Section;
 exports.Select = Select;
 exports.TabItem = TabItem;
+exports.Table = Table;
+exports.TableCell = TableCell;
+exports.TableHeadCell = TableHeadCell;
+exports.TableRow = TableRow;
 exports.Tabs = Tabs;
 exports.Tag = Tag;
 exports.TextArea = TextArea;