HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.
Search
-
Re: Adding new message types
For consistency sake it makes sense that formatter are predicable and backward compatible. As there are different markdown flavours, it makes sense to label them differently. There are other way to override the formatters due to he way vanilla auto-loads, I just don't think it is relevant to this case. Like the quotes… -
Re: Adding new message types
Yes, that's great guys. I could definitely come up with something that works through some combination of pre and post-processing. Can I draw your attention for one sec to the fact the Markdown formatter is intended to be extensible in an object-orientated fashion, it's just the code which includes it with a require_once… -
Re: Adding new message types
I wouldn't fork vanilla entirely to do this, you are bit left out in the cold having to support the entire code base just for one feature. You have the option of plugin. Fist consider if using processing.js is going to have its own Format Type, or something you could be within other Types such with a short code (like…
3 results