mirror of
https://github.com/discourse/discourse.git
synced 2024-12-02 09:53:45 +08:00
70f7c0ee6f
This commit changes the API for registering the plugin config page nav configuration from a server-side to a JS one; there is no need for it to be server-side. It also makes some changes to allow for 2 different ways of displaying navigation for plugin pages, depending on complexity: * TOP - This is the best mode for simple plugins without a lot of different custom configuration pages, and it reuses the grey horizontal nav bar already used for admins. * SIDEBAR - This is better for more complex plugins; likely this won't be used in the near future, but it's readily available if needed There is a new AdminPluginConfigNavManager service too to manage which plugin the admin is actively viewing, otherwise we would have trouble hiding the main plugin nav for admins when viewing a single plugin.
26 lines
717 B
JavaScript
26 lines
717 B
JavaScript
import Route from "@ember/routing/route";
|
|
import { inject as service } from "@ember/service";
|
|
import { ajax } from "discourse/lib/ajax";
|
|
import { sanitize } from "discourse/lib/text";
|
|
import AdminPlugin from "admin/models/admin-plugin";
|
|
|
|
export default class AdminPluginsShowRoute extends Route {
|
|
@service router;
|
|
@service adminPluginNavManager;
|
|
|
|
model(params) {
|
|
const pluginId = sanitize(params.plugin_id).substring(0, 100);
|
|
return ajax(`/admin/plugins/${pluginId}.json`).then((plugin) => {
|
|
return AdminPlugin.create(plugin);
|
|
});
|
|
}
|
|
|
|
afterModel(model) {
|
|
this.adminPluginNavManager.currentPlugin = model;
|
|
}
|
|
|
|
deactivate() {
|
|
this.adminPluginNavManager.currentPlugin = null;
|
|
}
|
|
}
|