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
Above creates a parser package so you could replace Markdown parser we use, or in this case, add wiki support. There could be other types like plugin or extension or some other name that is a general extension of EE. By default it'd run it as a plugin, but offer alternatives like parser to change more of the core code programmatically and without worry about breakages during upgrades.
The text was updated successfully, but these errors were encountered:
I like this better than specifying a type and instead just give them hooks into the processor in the extension. Something like on('onBeforeParse', function(e, data)){}' where data or something could hold the parsing data. Then you could do like return data.replace('foo', 'bar') and it'll give it back to EE? Not sure... @johnmdonahue, thoughts?
I want to enable 3rd party devs to easily script EE not just with the normal public API, but through packages or plugins. Ideas?
I have this idea currently:
Above creates a
parser
package so you could replace Markdown parser we use, or in this case, add wiki support. There could be other types likeplugin
orextension
or some other name that is a general extension of EE. By default it'd run it as aplugin
, but offer alternatives likeparser
to change more of the core code programmatically and without worry about breakages during upgrades.The text was updated successfully, but these errors were encountered: