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

[proposal] Remove dsl package #177

Closed
dwisiswant0 opened this issue Mar 26, 2024 · 0 comments · Fixed by #178
Closed

[proposal] Remove dsl package #177

dwisiswant0 opened this issue Mar 26, 2024 · 0 comments · Fixed by #178
Assignees
Labels

Comments

@dwisiswant0
Copy link
Collaborator

Summary

The dsl package will be removed from the codebase and migrated into a new repository, https://github.com/teler-sh/dsl.

Motivation

The current codebase has become too complex, and maintaining the dsl package within it has become increasingly difficult. Migrating the dsl package into its own repository will help in better organization, management, and versioning of this specific functionality. It will also facilitate easier collaboration and contribution from external parties who may only be interested in the DSL aspect.

Design

The dsl package will be extracted from the existing codebase and placed into its own repository. This will involve creating a new repository dedicated to the dsl (done at https://github.com/teler-sh/dsl) package and transferring all relevant code, documentation, and tests into it. The package will then be published as a standalone module, allowing it to be independently versioned and distributed.

Drawbacks

  • Increased complexity in managing multiple repositories.
  • Potential fragmentation of documentation and contribution efforts.
  • Additional overhead in maintaining separate versions for the dsl package.

Alternative Approaches

An alternative approach would be to refactor the existing codebase to simplify the dsl package within it. However, given the current complexity of the codebase, this may not be a feasible solution and could lead to further complications.

Unresolved Questions

What parts of the design are still undecided? Are there any outstanding questions or concerns that need to be addressed? For instance:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant