@ferlab/ui

@ferlab-ui React core components

Install

npm i @ferlab/ui

Developper

• All work must be done based on master
• All styles automatically reference to the @ferlab/styles package
• Components should be added and tests in storybook

Development

Steps to develop or debug the libraries in a real project

1. Make @ferlab/ui accessible to link
   1. npm link inside @ferlab/ui folder
2. Link the libraries in your project
   1. npm link @ferlab/ui

Duplicate React

TsConfig solution

Linking the library will add the packages twice in the bundle, which could create some issues with react and react-dom. It's important to add an alias to use the host modules.

e.g. in tsconfig | please refer to clin-portal-ui for a working example.

{
    "compilerOptions": {
        "baseUrl": ".",
        "paths": {
            "react": ["node_modules/react"],
            "react-dom": ["node_modules/react-dom"]
        }
    }
}

Other solution:

npm link the project node_modules/react into ferlab/ui

Npm link solution

This problem can also come up when you use npm link or an equivalent. In that case, your bundler might “see” two Reacts — one in application folder and one in your library folder. Assuming myapp and mylib are sibling folders, one possible fix is to run npm link ../myapp/node_modules/react from mylib. This should make the library use the application’s React copy.

Storybook

In order to see and test all available components

First you need to build the components

npm run build

or run in development mode

npm start

cd ferlab-ui/storybook
npm start

Publish new release

Updating antd

antd sometimes has breaking changes in non-breaking realease. To reduce the risk of blocking development in multiple project. We should follow the steps to update anything related to ant design.

1. Create a pr only containing antd updates
2. Create a npm release candidate e.g. 7.9.10-rc1
3. Push the RC release on portals in production (clin, kidsfirst) mininum.

   Clin has feature branch QA environnement, no need to release in QA.

Merging new changes

1. update the version of the package in package.json (https://semver.org)
2. Update the Release.md file with the changes
3. Add or modify storybook that matches your changes
4. Create a PR

Publish to npm

Description: This section outlines the process of publishing a package to npm. The publication is automatically triggered when a branch is merged into the master branch. If the package version already exists, the publish process will be skipped to avoid conflicts.

Steps:

1. Update the package.json version to the desired version for the release.
2. Create a pull request (PR) for the changes.
3. After reviewing the changes, merge the PR into the master branch.
4. Ensure that the GitHub actions have completed successfully before proceeding.

Publish a Release Candidate (RC)

Description: The purpose of a Release Candidate (RC) is to thoroughly test changes before merging them into the main branch. It allows specific changes to be tested in a feature branch before becoming part of the official release.

Steps:

1. A feature branch will be automatically created when a pull request is initiated.
2. In the feature branch, add a package.json version with a suffix -rc[number], such as 8.5.6-rc2, to indicate that it is a Release Candidate.
3. Mark the PR as 'NOT READY TO MERGE' to indicate that it should not be merged into the master branch.
4. The RC PR should be tested and validated, but it should not be merged into the master branch. Its purpose is to ensure thorough testing before proceeding with the official release.

Publish to npm Manually (in case of error with auto publish)

1. Try to install the package to make sure everything work corretly

   cd [test dir] && npm i [full_path]/ferlab-ui/packages/ui

2. Delete core folder to remove deleted files

   rm -rf core/

3. Prepare the package

   npm run build

4. Push the new version

5. Create a tag to the new version git tag ui@[semantic version] e.g.

   git tag ui@4.4.1 git push --tags

6. Login to npm

   npm login

7. Push the new version

   npm publish

Development

Run npx tscp -w to live-watch sass file.

Styles and themes

Strategy

1. Use .less to customize colors and ant design components
2. Export to scss for the main theme and custom components
3. Use one css module and scss per component
4. Use scss exported variables for props and inline styling (should be avoid when possible)

Naming convention for colors variables should follow ant design theme implementation

Motivation

• Access to the theme variables in JS
• Access of the theme variables in css module + scss
• Compatibility with other projects and component reusability
• Dont force CRA eject

Structure

[project]
  |-- theme/                :> Legacy styles
  |-- style/                :> Main style/theme source
    |-- dist/               :> dynamicaly generated files
      |-- themes
        |-- default/        :> default theme, to load in code
          |-- antd.css      :> load in main app, rewrite ant design default
          '-- _colors.scss   :> dynamically generated colors from ant design theme in colors.less
    |-- themes/
      |-- default           :> default theme (default could for example point to v1 or v2 etc.)
        |-- antd/           :> not use directly in the code
        | |-- antd.less
        | '-- colors.less
        |-- _colors.scss        :> Ant design colors to import from other scss files or JavaScript
        |-- colors.modules.scss :> Colors classes and variables to be uses inside jsx (className)
        '-- main.scss      :> General style for the site outside ant design component

everything in legacy src/theme/ should go in src/style/theme/default/main.scss or src/style/theme/default/colors.scss

Configuration

References

Ant Design available theme variables

Use

First import ant design override in the main application file

import 'themes/dist/themes/default/antd.css';
import 'themes/default/main.scss';

Components

1. Create a [Component].module.scss file in the same directory
2. Import your style inside your components

import style from '[Component].module.css'
// ...
return () => <div clasName={style.isBeautiful}></div>;

1. To use globaly defined theme variables, load theme from src/themes/default/colors.scss or src/themes/default/main.scss

How to export scss variables to JavaScript

inside a scss file, use the export key to make them available to JavaScript. Use the same technique as component .module.scss import in JS.

e.g.

:export {
    btnPrimaryBg: $btn-primary-bg;
    btnPrimaryColor: $btn-primary-color;
}

Link Issues:

In packages/ui:
rm -rf core
npm i
npm run build
npm remove --global @ferlab/ui
npm link
npm link ~/[project path]/nodes-module/react

Then in local projet:
npm unlink @ferlab/ui
npm link @ferlab/ui
npm start