Optimize bcrs-shared-components

shabeeb-aot commented 2 years ago

What is the problem?

When we implement bcrs-shared-components staff comment in FAS UI, we found some issues. Parent application must have following folders/files app/src/assets/styles/theme.scss app/src/mixins/index.ts app/src/interfaces/index.ts

What is the impact?

When some one is trying to use bcrs-shared-components they have to create these folder to work components

Proposed solution

Create production ready build Lerna support Rollup to build/minfy and extract css individual component. (Need to do a research)
Alternate approch

use common scss and convert to css on build, import in project use utils instead of mixins.

severinbeauvais commented 1 year ago

~This ticket needs some research (maybe a few days) to investigate what is possible and what impacts this will have to our UIs.~ see RFC ticket linked as a blocker

severinbeauvais commented 1 year ago

@jonathan-longe FYI

severinbeauvais commented 1 year ago

This is obviously not Priority 1 as we haven't worked on it for 1 year.

Travis and I will look at this as we look at upgrading the shared components for Vue3. No need for more visibility.

bcgov / entity