discourse-solved/config/routes.rb

# frozen_string_literal: true

DiscourseSolved::Engine.routes.draw do
  post "/accept" => "answer#accept"
  post "/unaccept" => "answer#unaccept"

  get "/by_user" => "solved_topics#by_user"
end

Discourse::Application.routes.draw { mount ::DiscourseSolved::Engine, at: "solution" }
DEV: Autoload and segregate features to prep for migration (#341) This commit autoloads plugin files, and also extracts features into their own modules. - `plugin.rb` is smaller - external plugins like discourse-automation and discourse-assign have their own entrypoints - solved filters as well 2025-03-21 11:45:19 +08:00			`# frozen_string_literal: true`

			`DiscourseSolved::Engine.routes.draw do`
			`post "/accept" => "answer#accept"`
			`post "/unaccept" => "answer#unaccept"`
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
			`get "/by_user" => "solved_topics#by_user"`
DEV: Autoload and segregate features to prep for migration (#341) This commit autoloads plugin files, and also extracts features into their own modules. - `plugin.rb` is smaller - external plugins like discourse-automation and discourse-assign have their own entrypoints - solved filters as well 2025-03-21 11:45:19 +08:00			`end`

			`Discourse::Application.routes.draw { mount ::DiscourseSolved::Engine, at: "solution" }`