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
Please consider including the Transport plugin in the standard wiki distribution.
I have been holding onto this hoping to work out better plugin catalog mechanisms but don't want to hold it up any longer. Instead I would like to establish criteria by which we would accept new plugins.
There is one outstanding issue regarding possible error handling and possible CORS issues too. It is my judgement that we will see more Transporters if the capability to invoke them is widely available. Experience will dictate what development/debugging support will be appropriate.
I am happy to invoke whatever github and npm ownership transfers are appropriate. Help me develop a checklist for such transfers. Thank you.
The text was updated successfully, but these errors were encountered:
Please consider including the Transport plugin in the standard wiki distribution.
I have been holding onto this hoping to work out better plugin catalog mechanisms but don't want to hold it up any longer. Instead I would like to establish criteria by which we would accept new plugins.
https://github.com/WardCunningham/wiki-plugin-transport
https://www.npmjs.com/package/wiki-plugin-transport
There is one outstanding issue regarding possible error handling and possible CORS issues too. It is my judgement that we will see more Transporters if the capability to invoke them is widely available. Experience will dictate what development/debugging support will be appropriate.
I am happy to invoke whatever github and npm ownership transfers are appropriate. Help me develop a checklist for such transfers. Thank you.
The text was updated successfully, but these errors were encountered: