discourse-service-authoring

To write a Discourse service object following SOLID principles, use a structured, multi-phase development process covering assessment, implementation, quality checks, business logic review, security audits, and RSpec testing. This enforces idiomatic Ruby and Discourse-specific architectural patterns.

Refactoring a Discourse controller action into a service object requires a phased approach: understanding the logic, assessing the scope, implementing the service, and running quality, business logic, and security reviews. This ensures the new service is maintainable, secure, and well-tested.

Adding RSpec tests and security checks to a Ruby service object involves dedicated testing and security audit phases. These phases enforce strict checklists to verify business logic correctness and security vulnerabilities, ensuring the service meets Discourse development standards.

This structured development process is Discourse-specific, tailored to Discourse service objects and architectural patterns. While it promotes SOLID principles and idiomatic Ruby generally, the checklists, audits, and conventions are designed for the Discourse platform.

Discourse service objects fail code quality checks during refactoring when they do not adhere to strict quality assurance checklists or SOLID principles. A multi-phase review process covering business logic, security, and idiomatic Ruby ensures the service passes these standards.