github-mirror/discourse
2
0
Fork 0
mirror of https://github.com/discourse/discourse.git synced 2024-12-25 14:03:42 +08:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity
357189d9e7
discourse/plugins/discourse-details/assets/javascripts/initializers/apply-details.js

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

31 lines
705 B
JavaScript
Raw Normal View History

DEV: Fix "ember/no-global-jquery" lint (#24586)
2023-11-28 17:53:38 +08:00
import $ from "jquery";
missing prettified files
2018-06-16 00:42:20 +08:00
import { withPluginApi } from "discourse/lib/plugin-api";
DEV: Consolidate i18n import paths (#29804) Enables our new eslint rules which enforce consistent i18n imports. For more info, see https://github.com/discourse/lint-configs/commit/0d58b40cd7d170a9f70bcef5c173f95eeb498298
2024-11-20 04:45:18 +08:00
import { i18n } from "discourse-i18n";
add discourse-details plugin
2015-11-30 18:32:01 +08:00
Add details to popup menu options.
2016-06-16 21:25:18 +08:00
function initializeDetails(api) {
DEV: Remove the <details> polyfill (#10260) Per the linked site (http://mths.be/details) and https://caniuse.com/#feat=details the <details> element is supported since Chrome 12/Safari 6/Firefox 49/Edge 79. IE 11 doesn't handle them, but we dropped the support for that browser.
2020-07-20 19:18:00 +08:00
api.decorateCooked(($elem) => $("details", $elem), {
FIX: Memory Leaks when decorating posts (#7749) * Remove long-deprecated method * FIX: Memory Leaks when decorating posts Previously we'd keep creating mixins dynamically when decorating the same class. This code changes the API to recommend an `id` parameter for each decorator which will avoid leaks. All plugins should be updated to include this parameter, although if they don't in the meantime it'll just mean a warning in the console (and a continued leak.)
2019-06-11 23:21:23 +08:00
id: "discourse-details",
});
Add details to popup menu options.
2016-06-16 21:25:18 +08:00
DEV: Improve `addToolbarPopupMenuOptionsCallback` plugin api (#23769) Why this change? Previously just using the `addToolbarPopupMenuOptionsCallback` plugin API itself was insufficient because it required the return object to include an `action` key which only accepted a name of the action function as a string. This was highly problematic because the action function had to be defined on the `composer` service which means using the `modifyClass` API to add the action function. This made the API awkward to use leading to poor developer experiencec. What does this change do? This commit introduces a couple of improvemnts to the API. 1. First the API has been renamed to `addComposerToolbarPopupMenuOption` because the API no longer accepts a callback function which was quite redundant. Instead, it now accepts an Object. The `addToolbarPopupMenuOptionsCallback` API function is deprecated and will be dropped in Discourse 3.3. Note that passing the API a function is still supported but will be dropped when the `addToolbarPopupMenuOptionsCallback` is removed. 2. The `action` key in the Object passed to the function can now be a function and is passed the `toolbarEvent` object when called. 3. The `condition` on key in the Object passed to the function can now be a function and is passed the `composer` service when called.
2023-10-06 07:43:40 +08:00
api.addComposerToolbarPopupMenuOption({
action: function (toolbarEvent) {
toolbarEvent.applySurround(
DEV: Consolidate i18n import paths (#29804) Enables our new eslint rules which enforce consistent i18n imports. For more info, see https://github.com/discourse/lint-configs/commit/0d58b40cd7d170a9f70bcef5c173f95eeb498298
2024-11-20 04:45:18 +08:00
"\n" + `[details="${i18n("composer.details_title")}"]` + "\n",
DEV: Improve `addToolbarPopupMenuOptionsCallback` plugin api (#23769) Why this change? Previously just using the `addToolbarPopupMenuOptionsCallback` plugin API itself was insufficient because it required the return object to include an `action` key which only accepted a name of the action function as a string. This was highly problematic because the action function had to be defined on the `composer` service which means using the `modifyClass` API to add the action function. This made the API awkward to use leading to poor developer experiencec. What does this change do? This commit introduces a couple of improvemnts to the API. 1. First the API has been renamed to `addComposerToolbarPopupMenuOption` because the API no longer accepts a callback function which was quite redundant. Instead, it now accepts an Object. The `addToolbarPopupMenuOptionsCallback` API function is deprecated and will be dropped in Discourse 3.3. Note that passing the API a function is still supported but will be dropped when the `addToolbarPopupMenuOptionsCallback` is removed. 2. The `action` key in the Object passed to the function can now be a function and is passed the `toolbarEvent` object when called. 3. The `condition` on key in the Object passed to the function can now be a function and is passed the `composer` service when called.
2023-10-06 07:43:40 +08:00
"\n[/details]\n",
"details_text",
{ multiline: false }
);
Add details to popup menu options.
2016-06-16 21:25:18 +08:00
},
DEV: Improve `addToolbarPopupMenuOptionsCallback` plugin api (#23769) Why this change? Previously just using the `addToolbarPopupMenuOptionsCallback` plugin API itself was insufficient because it required the return object to include an `action` key which only accepted a name of the action function as a string. This was highly problematic because the action function had to be defined on the `composer` service which means using the `modifyClass` API to add the action function. This made the API awkward to use leading to poor developer experiencec. What does this change do? This commit introduces a couple of improvemnts to the API. 1. First the API has been renamed to `addComposerToolbarPopupMenuOption` because the API no longer accepts a callback function which was quite redundant. Instead, it now accepts an Object. The `addToolbarPopupMenuOptionsCallback` API function is deprecated and will be dropped in Discourse 3.3. Note that passing the API a function is still supported but will be dropped when the `addToolbarPopupMenuOptionsCallback` is removed. 2. The `action` key in the Object passed to the function can now be a function and is passed the `toolbarEvent` object when called. 3. The `condition` on key in the Object passed to the function can now be a function and is passed the `composer` service when called.
2023-10-06 07:43:40 +08:00
icon: "caret-right",
label: "details.title",
Add details to popup menu options.
2016-06-16 21:25:18 +08:00
});
}
add discourse-details plugin
2015-11-30 18:32:01 +08:00
export default {
name: "apply-details",
PluginAPI for more stable backwards compatibility going forward
2016-02-13 04:46:36 +08:00
initialize() {
DEV: Improve `addToolbarPopupMenuOptionsCallback` plugin api (#23769) Why this change? Previously just using the `addToolbarPopupMenuOptionsCallback` plugin API itself was insufficient because it required the return object to include an `action` key which only accepted a name of the action function as a string. This was highly problematic because the action function had to be defined on the `composer` service which means using the `modifyClass` API to add the action function. This made the API awkward to use leading to poor developer experiencec. What does this change do? This commit introduces a couple of improvemnts to the API. 1. First the API has been renamed to `addComposerToolbarPopupMenuOption` because the API no longer accepts a callback function which was quite redundant. Instead, it now accepts an Object. The `addToolbarPopupMenuOptionsCallback` API function is deprecated and will be dropped in Discourse 3.3. Note that passing the API a function is still supported but will be dropped when the `addToolbarPopupMenuOptionsCallback` is removed. 2. The `action` key in the Object passed to the function can now be a function and is passed the `toolbarEvent` object when called. 3. The `condition` on key in the Object passed to the function can now be a function and is passed the `composer` service when called.
2023-10-06 07:43:40 +08:00
withPluginApi("1.14.0", initializeDetails);
add discourse-details plugin
2015-11-30 18:32:01 +08:00
},
};
Reference in New Issue Copy Permalink