discourse/app/views/common/_discourse_publish_styleshe...

<%= discourse_stylesheet_link_tag 'publish', theme_id: nil %>

<%- Discourse.find_plugin_css_assets(include_official: allow_plugins?, include_unofficial: allow_third_party_plugins?, mobile_view: mobile_view?, desktop_view: !mobile_view?, request: request).each do |file| %>
  <%= discourse_stylesheet_link_tag(file) %>
<%- end %>

<%- if theme_id.present? %>
  <%= discourse_stylesheet_link_tag(mobile_view? ? :mobile_theme : :desktop_theme) %>
<%- end %>
Code review comments. 2021-06-17 22:16:26 -04:00			`<%= discourse_stylesheet_link_tag 'publish', theme_id: nil %>`
FEATURE: allows to to style published page with themes/plugins (#9570) 2020-04-28 12:24:24 -04:00
			`<%- Discourse.find_plugin_css_assets(include_official: allow_plugins?, include_unofficial: allow_third_party_plugins?, mobile_view: mobile_view?, desktop_view: !mobile_view?, request: request).each do \|file\| %>`
			`<%= discourse_stylesheet_link_tag(file) %>`
			`<%- end %>`

PERF: Eager load Theme associations in Stylesheet Manager. Before this change, calling `StyleSheet::Manager.stylesheet_details` for the first time resulted in multiple queries to the database. This is because the code was modelled in a way where each `Theme` was loaded from the database one at a time. This PR restructures the code such that it allows us to load all the theme records in a single query. It also allows us to eager load the required associations upfront. In order to achieve this, I removed the support of loading multiple themes per request. It was initially added to support user selectable theme components but the feature was never completed and abandoned because it wasn't a feature that we thought was worth building. 2021-06-15 02:57:17 -04:00			`<%- if theme_id.present? %>`
FEATURE: allows to to style published page with themes/plugins (#9570) 2020-04-28 12:24:24 -04:00			`<%= discourse_stylesheet_link_tag(mobile_view? ? :mobile_theme : :desktop_theme) %>`
			`<%- end %>`