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 16c6ab8661b38051b14d68297afdc8504bc1175b 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
..
2022-04-28 11:51:03 +02:00
2023-02-21 10:30:48 +01:00
2023-02-21 10:30:48 +01:00
2023-02-21 10:30:48 +01:00
2023-02-21 10:30:48 +01:00
2020-07-21 15:55:03 +08:00
2023-08-01 09:50:46 +01:00