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

Integrate best practices #39

Merged

Conversation

tanghel
Copy link
Contributor

@tanghel tanghel commented Apr 26, 2024

  • simplified config:
    • have a unified config file for all apps
    • possibility to load library-specific configs (e.g. libs/common)
    • provide config schema that is validated when the app starts
    • generate entities from config schema
  • implemented architectural restrictions using the eslint-boundaries component in the eslint file
  • simplified start of apps by providing one app-specific start command, with the possibility of overriding the environment (devnet, testnet, mainnet) and applying custom watch or debug fields
  • to differentiate between environments, instead of having an environment-specific config, now we provide an environment-specific env file where only the env-specific information is set
  • having a generic services component that contains all the business logic

@tanghel tanghel merged commit 621818d into main May 7, 2024
1 check passed
@tanghel tanghel deleted the SERVICES-2337-integrate-best-practices-into-template-service branch May 7, 2024 12:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant