Open rafalp opened 10 years ago
quote within quote will be max.
what should the behavior be when this limit is exceeded? don't allow the user to quote, throw away the oldest quote, throw away the newest quote, other?
You strip quotes that are nested within quote within quote. Then you should remove empty quotes and validate if message has content.
This will need changes in preparser and posting routines, which is why its assigned for 0.6 milestone, when posting routine will be rewritten from scratch and MD implementation will be cleaned up.
For record, Misago parser now lives in misago.markup app. So far its just simple wrapper for markdown that extends it with basic BBCode support ([b][u][i] so far, but more are planned).
Dear @rafalp
If I understand correctly, some problems will be resolved with upgrade to markdown>3.
I just started that. Patterns need refactoring because breaking change with introduction of InlineProcessor. And references says that it should be faster (parse what Python's Re cannot).
See 'Flexible inline' change... https://github.com/Python-Markdown/markdown/commit/d18c3d0acab0e7469c3284c897afcb61f9dd1fea
...and Processor which I told you about: https://github.com/Python-Markdown/markdown/blob/master/markdown/inlinepatterns.py#L595
Best!
This would be easy as pie to implement in Misago once AST-based parser is backported from v4 branch, in #1480
how deep is too deep?