A controller or controllers, that is the question.

[squaressolutions]

Select Topic Area

Product Feedback

Body

As a developer, I have to develop a controller for a view every time, It is tedious and troublesome! If you want to see how a controller for any views, please download this package to see how it works.

https://github.com/squaressolutions/soms

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[lucasbrasantos]

Hi @squaressolutions,

I understand your concern about creating a controller for every view—it can indeed feel repetitive in certain scenarios. Here are a few strategies to help streamline your development process and make it less tedious:

1. Adopt a Modular Approach

• Instead of creating a new controller for each view, consider grouping similar functionality into a shared controller or service.
• Use a design pattern like the MVC (Model-View-Controller) where the controller acts as an intermediary and handles shared logic effectively. For example, if multiple views perform similar CRUD operations, a single controller might suffice.

2. Use Code Generation Tools

• Tools like Yeoman, JHipster, or even custom CLI scripts can generate boilerplate code for controllers, saving time.
• Frameworks like Spring Boot (Java) or Rails (Ruby) also provide scaffolding tools to automate controller creation.

3. Refactor Common Logic

• Move repetitive logic into helper classes, middleware, or shared services, depending on your stack.
• This ensures that controllers remain lightweight and focused on view-specific tasks.

4. Explore Alternative Architectures

• If you're working with frameworks like React, Angular, or Vue, consider component-based architectures. These frameworks often delegate responsibilities to components or services, reducing the need for traditional controllers.

5. Leverage the Provided Package

• I see that you shared a link to your package: https://github.com/squaressolutions/soms.
  Ensure that your package showcases clear documentation and examples to help others see how it solves the problem you're addressing.

If you'd like, you can provide a bit more context about your development environment and specific challenges. That way, the community can offer more tailored advice.

Hope this helps! 🎉