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

[Feature Request] CLI Flow Control #311

Open
1 task done
Ujstor opened this issue Sep 30, 2024 · 0 comments
Open
1 task done

[Feature Request] CLI Flow Control #311

Ujstor opened this issue Sep 30, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@Ujstor
Copy link
Collaborator

Ujstor commented Sep 30, 2024

Tell us about your feature request

The idea is to add more control when features that are used depend on each other or are in contradiction.

Current examples are HTMX and Tailwind's advanced features. Tailwind depends on HTMX, and the HTMX code will be automatically generated. A better approach would be to not have Tailwind available at all in TUI if HTMX is not selected.

The same applies if a CLI command is used. Inform the user that the specified flag needs to be used with XY or that it is in conflict with XY, and do not create the project.

Another good use case is that if CRUD operations are implemented (#253 ), I don't see the point in doing it for Redis, and as an advanced option, this will not be available if redis as DBdriver is used. Also, if the DB driver flag is none, the advanced flag for CRUD will not be visible or available as a flag.

Currently, all features are complementary, there isn't a possibility for contradiction between them. However, having a mechanism that can handle such situations would be beneficial. #268 would be a good example

Disclaimer

  • I agree
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant