c139767055
In the past, the result of template compilation would be stored directly in `Ember.TEMPLATES`. Following the move to more modern ember-cli-based compilation, templates are now compiled to es6 modules. To handle forward/backwards compatibility during these changes we had logic in `discourse-boot` which would extract templates from the es6 modules and store them into the legacy-style `Ember.TEMPLATES` object. This commit removes that shim, and updates our resolver to fetch templates directly from es6 modules. This is closer to how 'vanilla' Ember handles template resolution. We still have a lot of discourse-specific logic, but now it is centralised in one location and should be easier to understand and normalize in future. This commit should not introduce any behaviour change.
24 lines
707 B
JavaScript
24 lines
707 B
JavaScript
import { acceptance, query } from "discourse/tests/helpers/qunit-helpers";
|
|
import { hbs } from "ember-cli-htmlbars";
|
|
import { test } from "qunit";
|
|
import { visit } from "@ember/test-helpers";
|
|
import { registerTemplateModule } from "discourse/tests/helpers/template-module-helper";
|
|
|
|
acceptance("CustomHTML template", function (needs) {
|
|
needs.hooks.beforeEach(() => {
|
|
registerTemplateModule(
|
|
"discourse/templates/top",
|
|
hbs`<span class='top-span'>TOP</span>`
|
|
);
|
|
});
|
|
|
|
test("renders custom template", async function (assert) {
|
|
await visit("/static/faq");
|
|
assert.strictEqual(
|
|
query("span.top-span").innerText,
|
|
"TOP",
|
|
"it inserted the template"
|
|
);
|
|
});
|
|
});
|