You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To make plugin development easier, we should be able to mark a plugin to get reloaded automatically from the filesystem if this is set. I think we don't want to check the filesystem on every call to a trigger to see if the modified time is changed on the file. However, if that is inexpensive to do, then we should do that. Otherwise, let's have a setting that puts a plugin in development mode, where it is reloaded from disk on every triggering of it.
The text was updated successfully, but these errors were encountered:
Adds the request plugin type. Triggers can be bound to an API endpoint at /api/v3/engine/<path>. Requests will get yielded to the plugin with the query parameters, request parameters, and request body.
I didn't implement the test endpoint for this plugin type as it seems much more natural for users to save the file and make a new request. Once #25863 is done it'll make it very easy.
Closes#25862
This updates plugins so that they will reload the code if the local file is modified. Github pugins continue to be loaded only once when they are initially created or loaded on startup.
This will make iterating on plugin development locally much easier.
Closes#25863
To make plugin development easier, we should be able to mark a plugin to get reloaded automatically from the filesystem if this is set. I think we don't want to check the filesystem on every call to a trigger to see if the modified time is changed on the file. However, if that is inexpensive to do, then we should do that. Otherwise, let's have a setting that puts a plugin in development mode, where it is reloaded from disk on every triggering of it.
The text was updated successfully, but these errors were encountered: