RSpec setup becomes harder to follow at either extreme: trivial fixture wrappers hide lifecycle and intent, while forcing every named operation inline repeats low-level protocol and configuration details. This change documents and applies a test-setup hierarchy: - use `fab!`, `let`, `let!`, `subject`, and inline `Fabricate` according to lifecycle and role; - use a small example-group method when parameterized behavior gives one spec useful vocabulary; - move helpers into auto-loaded `spec/support` only when they are shared across spec files; - use fabricators and page objects for the data shapes and system-test interfaces they own. Core and plugin support files are loaded centrally by `rails_helper`, so plugin-specific support loaders are unnecessary. The migration specs encountered during the sweep are removed according to repository policy; production migrations are unchanged. |
||
|---|---|---|
| .. | ||
| admin/assets/javascripts | ||
| app | ||
| assets | ||
| config | ||
| db | ||
| lib | ||
| public/images/upcoming_changes | ||
| spec | ||
| test/javascripts | ||
| about.json | ||
| package.json | ||
| plugin.rb | ||
| README.md | ||
| tsconfig.json | ||
Discourse Solved
Provides a solved button on designated categories
How to Install this Plugin
To install Discourse Plugin - https://meta.discourse.org/t/install-a-plugin/19157
How to Check if Plugin is installed
Go to Admin > Plugins
You should now see:
What to expect if Plugin is installed
Inside the Plugins, you will have the following options:
How to enable it in your posts
New Categories - Check ✅ Allow topic owner and staff to mark a reply as the solution
Old Categories - Go to that Category > Edit > Settings > Check ✅ Allow topic owner and staff to mark a reply as the solution
BONUS: How to add badges to those who answered correctly
https://meta.discourse.org/t/discourse-solved-accepted-answer-plugin/30155
License
MIT


