You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: