Skip to content

Enforce eslint rules for a component #7

@juri-sinitson

Description

@juri-sinitson

Component

Enforce common wrapper

Why/what to enforce?

  1. To avoid repeating the same routines for components (loading, message, data, etc.) again and again
  2. To be able to change the components for those routines on one places instead on countless

TODOs

Issue linting error when the following applies for a component:

  1. It isn't coming from the domain shared
  2. It has now common wrapper

Allow using the current UI library (e.g. PrimeNG) directly only in the domain shared

Why?

  1. To avoid tight coupling
  2. To have a clear set of possible UI blocks in our catalog
  3. As the case may be also other goals described in README.md

Metadata

Metadata

Assignees

Labels

buildChanges that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions