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
I suggest that we consider removing the book controller from the template by default. While the book controller serves as a valuable example, it may not be relevant to every project. For some users, its presence can add an initial layer of complexity, especially when they aim to begin with a clean slate. By making this change, we can provide a simpler and more customizable starting point for our template, catering to a broader spectrum of projects and developer needs.
Benefits:
Simplicity: Removing the book controller would reduce the initial complexity of the template, making it easier for users to get started.
Flexibility: Users can always add a book controller or any other specific functionality they need based on their project requirements. This change wouldn't limit their choices but instead offer a more open starting point.
Learning Curve: It could potentially lower the learning curve for beginners who might find the book controller example confusing if it doesn't align with their project goals.
Options:
To ensure backward compatibility and accommodate users who still prefer to have the book controller, we could introduce an option during project initialization to include it. This way, those who need it can opt for it, while it won't be part of the default template.
I would greatly appreciate your thoughts and feedback on this proposal. Your insights, suggestions, and concerns are invaluable to the community. Let's work together to make this template even more accessible and adaptable for all users! 😊
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello All,
I would like to suggest an enhancement for the template (https://github.com/create-go-app/fiber-go-template) that could make it even more user-friendly and adaptable to a wider range of projects.
Proposal:
I suggest that we consider removing the book controller from the template by default. While the book controller serves as a valuable example, it may not be relevant to every project. For some users, its presence can add an initial layer of complexity, especially when they aim to begin with a clean slate. By making this change, we can provide a simpler and more customizable starting point for our template, catering to a broader spectrum of projects and developer needs.
Benefits:
Simplicity: Removing the book controller would reduce the initial complexity of the template, making it easier for users to get started.
Flexibility: Users can always add a book controller or any other specific functionality they need based on their project requirements. This change wouldn't limit their choices but instead offer a more open starting point.
Learning Curve: It could potentially lower the learning curve for beginners who might find the book controller example confusing if it doesn't align with their project goals.
Options:
To ensure backward compatibility and accommodate users who still prefer to have the book controller, we could introduce an option during project initialization to include it. This way, those who need it can opt for it, while it won't be part of the default template.
I would greatly appreciate your thoughts and feedback on this proposal. Your insights, suggestions, and concerns are invaluable to the community. Let's work together to make this template even more accessible and adaptable for all users! 😊
Thank you for your time and consideration.
Best regards,
Shrijeeth S
Beta Was this translation helpful? Give feedback.
All reactions