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
{{ message }}
This repository has been archived by the owner on Nov 8, 2022. It is now read-only.
Similar to plugin diagnostics is stand-alone functionality something that should go in the plugin libraries or should it go in the Snap documentation? What are your opinions?
I think that documentation for stand-alone plugin should be in main Snap repo. New users takes a look at main repo and looks for features and stand-alone feature should work for all snap-plugin-libs.
I agree that information on how to use stand-alone plugins should go in Snap. Should we include information about how to write a stand-alone plugin in Snap or in the plugin-libs?
I think that information about how to write a stand-alone could be in plugin libs because there are small differences in implementation related to the programming languages
Missing documentation for stand-alone feature (at least I don't see it). Users should know how use stand-alone plugins.
The text was updated successfully, but these errors were encountered: