Package: sanic-plugin-toolkit
Welcome to the Sanic Plugin Toolkit.The Sanic Plugin Toolkit (SPTK) is a lightweight python library aimed at making it as simple as possible to build
plugins for the Sanic Async HTTP Server.The SPTK provides aSanicPluginpython base object that your plugin can build upon. It is set up with all of the basic
functionality that the majority of Sanic Plugins will need.A SPTK Sanic Plugin is implemented in a similar way to Sanic Blueprints. You can use convenience decorators to set up all
of the routes, middleware, exception handlers, and listeners your plugin uses in the same way you would a blueprint,
and any Application developer can import your plugin and register it into their application.The Sanic Plugin Toolkit is more than just a Blueprints-like system for Plugins. It provides an enhanced middleware
system, and manages Context objects.Notice:Please update to SPTK v0.90.1 if you need compatibility with Sanic v21.03+.The Enhanced Middleware SystemThe Middleware system in the Sanic Plugin Toolkit both builds upon and extends the native Sanic middleware system.
Rather than simply having two middleware queues (‘request’, and ‘response’), the middleware system in SPF uses five
additional queues.Request-Pre: These middleware runbeforethe application’s own request middleware.Request-Post: These middleware runafterthe application’s own request middleware.Response-Pre: These middleware runbeforethe application’s own response middleware.Response-Post: These middleware runafterthe application’s own response middleware.Cleanup: These middleware runafterall of the above middleware, and are run after a response is sent, and are run even if response is None.So as a plugin developer you can choose whether you need your middleware to be executed before or after the
application’s own middleware.You can also assign a priority to each of your plugin’s middleware so you can more precisely control the order in which
your middleware is executed, especially when the application is using multiple plugins.The Context Object ManagerOne feature that many find missing from Sanic is a context object. SPF provides multiple context objects that can be
used for different purposes.A shared context: All plugins registered in the SPF have access to a shared, persistent context object, which anyone can read and write to.A per-request context: All plugins get access to a shared temporary context object anyone can read and write to that is created at the start of a request, and deleted when a request is completed.A per-plugin context: All plugins get their own private persistent context object that only that plugin can read and write to.A per-plugin per-request context: All plugins get a temporary private context object that is created at the start of a request, and deleted when a request is completed.InstallationInstall the extension with using pip, or easy_install.$pipinstall-Usanic-plugin-toolkitUsageA simple plugin written using the Sanic Plugin Toolkit will look like this:# Source: my_plugin.pyfromsanic_plugin_toolkitimportSanicPluginfromsanic.responseimporttextclassMyPlugin(SanicPlugin):def__init__(self,*args,**kwargs):super(MyPlugin,self).__init__(*args,**kwargs)# do pre-registration plugin init here.# Note, context objects are not accessible here.defon_registered(self,context,reg,*args,**kwargs):# do post-registration plugin init here# We have access to our context and the shared context now.context.my_private_var="Private variable"shared=context.sharedshared.my_shared_var="Shared variable"my_plugin=MyPlugin()# You don't need to add any parameters to @middleware, for default behaviour# This is completely compatible with native Sanic middleware behaviour@my_plugin.middlewaredefmy_middleware(request)h=request.headers#Do request middleware things here#You can tune the middleware priority, and add a context param like this#Priority must be between 0 and 9 (inclusive). 0 is highest priority, 9 the lowest.#If you don't specify an 'attach_to' parameter, it is a 'request' middleware@my_plugin.middleware(priority=6,with_context=True)defmy_middleware2(request,context):context['test1']="test"print("Hello world")#Add attach_to='response' to make this a response middleware@my_plugin.middleware(attach_to='response',with_context=True)defmy_middleware3(request,response,context):# Do response middleware herereturnresponse#Add relative='pre' to make this a response middleware run _before_ the#application's own response middleware@my_plugin.middleware(attach_to='response',relative='pre',with_context=True)defmy_middleware4(request,response,context):# Do response middleware herereturnresponse#Add attach_to='cleanup' to make this run even when the Response is None.#This queue is fired _after_ response is already sent to the client.@my_plugin.middleware(attach_to='cleanup',with_context=True)defmy_middleware5(request,context):# Do per-request cleanup here.returnNone#Add your plugin routes here. You can even choose to have your context passed in to the route.@my_plugin.route('/test_plugin',with_context=True)deft1(request,context):words=context['test1']returntext('from plugin!{}'.format(words))The Application developer can use your plugin in their code like this:# Source: app.pyfromsanicimportSanicfromsanic_plugin_toolkitimportSanicPluginRealmfromsanic.responseimporttextimportmy_pluginapp=Sanic(__name__)realm=SanicPluginRealm(app)assoc=realm.register_plugin(my_plugin)# ... rest of user app hereThere is support for using a config file to define the list of plugins to load when SPF is added to an App.# Source: sptk.ini[plugins]MyPluginAnotherPlugin=ExampleArg,False,KWArg1=True,KWArg2=33.3# Source: app.pyapp=Sanic(__name__)app.config['SPTK_LOAD_INI']=Trueapp.config['SPTK_INI_FILE']='sptk.ini'realm=SanicPluginRealm(app)# We can get the assoc object from SPF, it is already registeredassoc=spf.get_plugin_assoc('MyPlugin')Or if the developer prefers to do it the old way, (like the Flask way), they can still do it like this:# Source: app.pyfromsanicimportSanicfromsanic.responseimporttextfrommy_pluginimportMyPluginapp=Sanic(__name__)# this magically returns your previously initialized instance# from your plugin module, if it is named `my_plugin` or `instance`.assoc=MyPlugin(app)# ... rest of user app hereContributingQuestions, comments or improvements? Please create an issue onGithubCreditsAshley Sommerashleysommer@gmail.com