Struct perseus::plugins::FunctionalPluginActions
source · pub struct FunctionalPluginActions {
pub tinker: FunctionalPluginAction<(), ()>,
pub settings_actions: FunctionalPluginSettingsActions,
pub build_actions: FunctionalPluginBuildActions,
pub export_actions: FunctionalPluginExportActions,
pub export_error_page_actions: FunctionalPluginExportErrorPageActions,
pub server_actions: FunctionalPluginServerActions,
pub client_actions: FunctionalPluginClientActions,
}
Expand description
Actions designed to be compatible with other plugins such that two plugins can execute the same action.
Fields§
§tinker: FunctionalPluginAction<(), ()>
The all-powerful action that can modify the Perseus engine itself.
Because modifying the code you’re running doesn’t work with compiled
languages like Rust, this has its own command in the CLI, perseus tinker
. This is best used for modifying .perseus/Cargo.toml
or
other files. Ensure that you add signal comments so you don’t apply the
same modifications twice! This will be executed in the context of
.perseus/
. As usual, do NOT change the directory here, because that
will affect every other plugin as well, just use ../
s if you need
to work outside .perseus/
.
If your plugin uses this action in a way that may confuse other plugins, you should note this in your documentation.
settings_actions: FunctionalPluginSettingsActions
Actions pertaining to the modification of settings created with
PerseusApp
.
build_actions: FunctionalPluginBuildActions
Actions pertaining to the build process.
export_actions: FunctionalPluginExportActions
Actions pertaining to the export process.
export_error_page_actions: FunctionalPluginExportErrorPageActions
Actions pertaining to the process of exporting an error page.
server_actions: FunctionalPluginServerActions
Actions pertaining to the server.
client_actions: FunctionalPluginClientActions
Actions pertaining to the client-side code.