2021-04-28 15:12:08 -05:00
|
|
|
<!DOCTYPE html>
|
|
|
|
|
<html>
|
|
|
|
|
<head>
|
|
|
|
|
<title>Theme QUnit Test Runner</title>
|
|
|
|
|
<%= discourse_color_scheme_stylesheets %>
|
2022-11-17 11:44:44 -06:00
|
|
|
<meta name="color-scheme" content="light dark">
|
|
|
|
|
|
2023-09-11 03:12:37 -05:00
|
|
|
<%- if @has_test_bundle && !@suggested_themes %>
|
2022-06-20 09:33:05 -05:00
|
|
|
<%= preload_script "vendor" %>
|
DEV: introduce Embroider behind a flag, and start testing in CI (#23005)
Discourse core now builds and runs with Embroider! This commit adds
the Embroider-based build pipeline (`USE_EMBROIDER=1`) and start
testing it on CI.
The new pipeline uses Embroider's compat mode + webpack bundler to
build discourse code, and leave everything else (admin, wizard,
markdown-it, plugins, etc) exactly the same using the existing
Broccoli-based build as external bundles (<script> tags), passed
to the build as `extraPublicTress` (which just means they get
placed in the `/public` folder).
At runtime, these "external" bundles are glued back together with
`loader.js`. Specifically, the external bundles are compiled as
AMD modules (just as they were before) and registered with the
global `loader.js` instance. They expect their `import`s (outside
of whatever is included in the bundle) to be already available in
the `loader.js` runtime registry.
In the classic build, _every_ module gets compiled into AMD and
gets added to the `loader.js` runtime registry. In Embroider,
the goal is to do this as little as possible, to give the bundler
more flexibility to optimize modules, or omit them entirely if it
is confident that the module is unused (i.e. tree-shaking).
Even in the most compatible mode, there are cases where Embroider
is confident enough to omit modules in the runtime `loader.js`
registry (notably, "auto-imported" non-addon NPM packages). So we
have to be mindful of that an manage those dependencies ourselves,
as seen in #22703.
In the longer term, we will look into using modern features (such
as `import()`) to express these inter-dependencies.
This will only be behind a flag for a short period of time while we
perform some final testing. Within the next few weeks, we intend
to enable by default and remove the flag.
---------
Co-authored-by: David Taylor <david@taylorhq.com>
2023-09-07 07:15:43 -05:00
|
|
|
<%= preload_script "test-support" %>
|
|
|
|
|
<%= preload_script "discourse-for-tests" %>
|
DEV: convert I18n pseudo package into real package (discourse-i18n) (#23867)
Currently, `window.I18n` is defined in an old school hand written
script, inlined into locale/*.js by the Rails asset pipeline, and
then the global variable is shimmed into a pseudo AMD module later
in `module-shims.js`.
This approach has some problems – for one thing, when we add a new
V2 addon (e.g. in #23859), Embroider/Webpack is stricter about its
dependencies and won't let you `import from "I18n";` when `"I18n"`
isn't listed as one of its `dependencies` or `peerDependencies`.
This moves `I18n` into a real package – `discourse-i18n`. (I was
originally planning to keep the `I18n` name since it's a private
package anyway, but NPM packages are supposed to have lower case
names and that may cause problems with other tools.)
This package defines and exports a regular class, but also defines
the default global instance for backwards compatibility. We should
use the exported class in tests to make one-off instances without
mutating the global instance and having to clean it up after the
test run. However, I did not attempt that refactor in this PR.
Since `discourse-i18n` is now included by the app, the locale
scripts needs to be loaded after the app chunks. Since no "real"
work happens until later on when we kick things off in the boot
script, the order in which the script tags appear shouldn't be a
problem. Alternatively, we can rework the locale bundles to be more
lazy like everything else, and require/import them into the app.
I avoided renaming the imports in this commit since that would be
quite noisy and drowns out the actual changes here. Instead, I used
a Webpack alias to redirect the current `"I18n"` import to the new
package for the time being. In a separate commit later on, I'll
rename all the imports in oneshot and remove the alias. As always,
plugins and the legacy bundles (admin/wizard) still relies on the
runtime AMD shims regardless.
For the most part, I avoided refactoring the actual I18n code too
much other than making it a class, and some light stuff like `var`
into `let`.
However, now that it is in a reasonable format to work with (no
longer inside the global script context!) it may also be a good
opportunity to refactor and make clear what is intended to be
public API vs internal implementation details.
Speaking of, I took the librety to make `PLACEHOLDER`, `SEPARATOR`
and `I18nMissingInterpolationArgument` actual constants since it
seemed pretty clear to me those were just previously stashed on to
the `I18n` global to avoid polluting the global namespace, rather
than something we expect the consumers to set/replace.
2023-10-12 08:44:01 -05:00
|
|
|
<%= preload_script "locales/#{I18n.locale}" %>
|
2021-04-28 15:12:08 -05:00
|
|
|
<%= preload_script "admin" %>
|
2022-08-22 03:56:39 -05:00
|
|
|
<%- Discourse.find_plugin_js_assets(include_disabled: true).each do |file| %>
|
|
|
|
|
<%= preload_script file %>
|
|
|
|
|
<%- end %>
|
2022-11-07 18:23:43 -06:00
|
|
|
<%= preload_script "test-site-settings" %>
|
2021-04-28 15:12:08 -05:00
|
|
|
<%= theme_translations_lookup %>
|
|
|
|
|
<%= theme_js_lookup %>
|
|
|
|
|
<%= theme_lookup("head_tag") %>
|
|
|
|
|
<%= theme_tests %>
|
2022-07-11 05:01:47 -05:00
|
|
|
|
2021-04-28 15:12:08 -05:00
|
|
|
<%= tag.meta id: 'data-discourse-setup', data: client_side_setup_data %>
|
|
|
|
|
<meta property="og:title" content="">
|
|
|
|
|
<meta property="og:url" content="">
|
2022-01-13 14:16:34 -06:00
|
|
|
<meta name="discourse/config/environment" content="<%=u discourse_config_environment(testing: true) %>" />
|
2022-07-11 05:01:47 -05:00
|
|
|
|
|
|
|
|
<style>
|
2023-04-20 07:57:40 -05:00
|
|
|
<%= File.read("#{Rails.root}/app/assets/javascripts/node_modules/qunit/qunit/qunit.css").html_safe %>
|
2022-07-11 05:01:47 -05:00
|
|
|
</style>
|
2022-11-17 11:44:44 -06:00
|
|
|
|
|
|
|
|
<%= discourse_stylesheet_link_tag(:desktop, theme_id: nil) %>
|
|
|
|
|
<%= discourse_stylesheet_link_tag("qunit-custom", theme_id: nil) %>
|
2021-04-28 15:12:08 -05:00
|
|
|
<%- else %>
|
|
|
|
|
<style>
|
|
|
|
|
html {
|
|
|
|
|
font-family: Arial;
|
|
|
|
|
}
|
|
|
|
|
</style>
|
|
|
|
|
<%- end %>
|
2022-07-11 05:01:47 -05:00
|
|
|
|
2022-04-22 09:04:01 -05:00
|
|
|
<%- if params['testem'] %>
|
2022-06-20 23:44:31 -05:00
|
|
|
<script defer src="/assets/testem.js"></script>
|
2022-04-22 09:04:01 -05:00
|
|
|
<%- end %>
|
2021-04-28 15:12:08 -05:00
|
|
|
</head>
|
|
|
|
|
<body>
|
2023-09-11 03:12:37 -05:00
|
|
|
<%- if !@has_test_bundle %>
|
|
|
|
|
This is a production installation of Discourse, and cannot be used for theme testing.
|
|
|
|
|
For more information, see <a href="https://meta.discourse.org/t/66857">this guide</a>.
|
|
|
|
|
<% elsif @suggested_themes %>
|
2021-05-11 09:45:07 -05:00
|
|
|
<h2>Theme QUnit Test Runner</h2>
|
2022-07-11 05:01:47 -05:00
|
|
|
|
2021-05-11 09:45:07 -05:00
|
|
|
<%- if @suggested_themes.size == 0 %>
|
|
|
|
|
<p>Cannot find any theme tests.</p>
|
|
|
|
|
<%- else %>
|
|
|
|
|
<h3>Select a theme/component: </h3>
|
|
|
|
|
<%- @suggested_themes.each do |(id, name)| %>
|
2022-06-21 05:32:46 -05:00
|
|
|
<h4><%= link_to name, theme_qunit_path(id: id) %></h4>
|
2021-05-11 09:45:07 -05:00
|
|
|
<%- end %>
|
2021-04-28 15:12:08 -05:00
|
|
|
<%- end %>
|
2023-09-11 03:12:37 -05:00
|
|
|
<% else %>
|
2022-07-10 03:52:29 -05:00
|
|
|
<%= preload_script "scripts/discourse-test-listen-boot" %>
|
|
|
|
|
<%= preload_script "scripts/discourse-boot" %>
|
|
|
|
|
<%- end %>
|
2021-04-28 15:12:08 -05:00
|
|
|
</body>
|
|
|
|
|
</html>
|
