Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enforce eslint rules for a component #7

Open
juri-sinitson opened this issue Dec 21, 2023 · 0 comments
Open

Enforce eslint rules for a component #7

juri-sinitson opened this issue Dec 21, 2023 · 0 comments
Assignees
Labels
build Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)

Comments

@juri-sinitson
Copy link
Owner

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
@juri-sinitson juri-sinitson added the build Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm) label Dec 21, 2023
@juri-sinitson juri-sinitson self-assigned this Dec 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
Projects
None yet
Development

No branches or pull requests

1 participant