discourse-solved/spec
Natalie Tay f96aceb5f4
FIX: Use SolvedTopics to list posts in /activity/solved instead of user actions (#376)
In https://github.com/discourse/discourse-solved/pull/342 we moved solutions away from topic_custom_fields into proper tables, with the tables as the proper source of truth to a topic's solution.

The user's /my/activity/solved route uses user_actions which is not accurate, and a user has reported a bug where their solution is not reflected there (user actions are not a good representation of what a topic's solution is). 

This commit introduces 
- a new route to get solutions, and is mindful `hide_user_profiles_from_public` and such settings
- also mindful of PMs and private categories
- a new template that makes use of the `<UserStream>` to load posts safely and avoid reimplementation
2025-07-02 16:56:12 +08:00
..
components DEV: Fix new Rubocop offenses 2024-03-06 10:25:26 +01:00
fabricators DEV: Move solved custom fields into a table (#342) 2025-03-25 14:51:32 +08:00
integration FIX: Accepting another answer does not commit (#360) 2025-04-07 11:42:36 +08:00
lib FIX: Exclude the first post itself when checking if an existing solution from the user exists (#378) 2025-07-02 11:45:14 +08:00
models FIX: User directory for solutions should update when value changes from positive value to zero (#372) 2025-06-11 10:46:36 +08:00
requests FIX: Use SolvedTopics to list posts in /activity/solved instead of user actions (#376) 2025-07-02 16:56:12 +08:00
serializers FIX: Standardise the definition of what a solution is (#352) 2025-03-28 09:49:02 +08:00
system FIX: Use SolvedTopics to list posts in /activity/solved instead of user actions (#376) 2025-07-02 16:56:12 +08:00