David Taylor 82b16f4f47 DEV: Do not manipulate theme module paths at build-time (#23148) ... Manipulating theme module paths means that the paths you author are not the ones used at runtime. This can lead to some very unexpected behavior and potential module name clashes. It also meant that the refactor in 16c6ab8661 was unable to correctly match up theme connector js/templates. While this could technically be a breaking change, I think it is reasonably safe because: 1. Themes are already forced to use relative paths when referencing their own modules (since they're namespaced based on the site-specific id). The only time this might be problematic is when theme tests reference modules in the theme's main `javascripts` directory 2. For things like components/services/controllers/etc. our custom Ember resolver works backwards from the end of the path, so adding `discourse/` in the middle will not affect resolution.		2023-08-18 18:15:23 +01:00
..
assets	DEV: Move PluginOutlet at bottom of TopicNavigation (#23149)	2023-08-18 11:41:09 -05:00
controllers	FIX: Pending post deletion by creator (#23130)	2023-08-18 15:30:59 +00:00
helpers	DEV: Correctly strip sourcemap URL from splash-screen js (#22879)	2023-07-31 16:49:27 +01:00
jobs	DEV: there is no need anymore to wrap export methods into enumerators (#22567)	2023-08-17 22:09:58 +04:00
mailers	FIX: Order tags shown in email subject by topics count and name (#22586)	2023-07-13 15:39:58 +08:00
models	DEV: Do not manipulate theme module paths at build-time (#23148)	2023-08-18 18:15:23 +01:00
serializers	DEV: Remove need for reloading cached summary thanks to Range#max (#23106)	2023-08-15 15:03:42 -03:00
services	DEV: Remove need for reloading cached summary thanks to Range#max (#23106)	2023-08-15 15:03:42 -03:00
views	PERF: Avoid calling the same translation twice when rendering lists view (#22976)	2023-08-04 13:38:41 +08:00