mirror of
https://github.com/discourse/discourse.git
synced 2025-01-18 11:32:46 +08:00
cfe4ff8d56
When returning the customRenderFn from within buildCustomMarkdownCookFunction for custom markdown engines (such as the one used by the [chat] transcripts) we were not hoisting/unhoisting the `html_raw` tokens created by the transcript, which meant that opts.discourse.hoisted could end up in a state where it was null, and which caused errors and general unpleasantness. Instead, we can just call the `cook` function that is already exported from discourse-markdown-it, that takes care of what we did previously plus the hoisting. There is a companion chat commit that adds tests for this, there are no custom markdown engine usages in core to test with. |
||
|---|---|---|
| .. | ||
| admin | ||
| confirm-new-email | ||
| discourse | ||
| discourse-common | ||
| discourse-hbr | ||
| discourse-widget-hbs | ||
| docs | ||
| ember-addons | ||
| locales | ||
| pretty-text | ||
| select-kit | ||
| truth-helpers | ||
| wizard | ||
| .npmrc | ||
| activate-account.js | ||
| admin.js.erb | ||
| app-boot.js | ||
| application.js | ||
| auto-redirect.js | ||
| browser-detect.js | ||
| browser-update.js | ||
| discourse-loader.js | ||
| discourse-shims.js | ||
| embed-application.js | ||
| ember_include.js.erb | ||
| ember_jquery.js | ||
| env.js | ||
| google-tag-manager.js | ||
| google-universal-analytics-v3.js | ||
| google-universal-analytics-v4.js | ||
| handlebars-shim.js | ||
| main_include_admin.js | ||
| markdown-it-bundle.js | ||
| onpopstate-handler.js | ||
| package.json | ||
| polyfills.js | ||
| pretty-text-bundle.js | ||
| print-page.js | ||
| service-worker.js.erb | ||
| set-prototype-polyfill.js | ||
| start-discourse.js | ||
| template_include.js | ||
| test-shims.js | ||
| vendor-common.js | ||
| vendor-theme-tests.js | ||
| vendor.js | ||
| widget-runtime.js | ||
| wizard-application.js | ||
| wizard-shims.js | ||
| wizard-start.js | ||
| wizard-vendor.js | ||
| yarn.lock | ||