Github user jablko commented on the issue:
https://github.com/apache/trafficserver/pull/1303
> The ``inliner`` parameter takes an instance of `states.Inliner` or a
subclass.
> It handles inline markup recognition. A common extension is the addition
of
> further implicit hyperlinks, like "RFC 2822". This can be done by
subclassing
> `states.Inliner`, adding a new method for the implicit markup, and adding
a
> ``(pattern, method)`` pair to the "implicit_dispatch" attribute of the
> subclass. See `states.Inliner.implicit_inline()` for details.
https://sourceforge.net/p/docutils/code/HEAD/tree/trunk/docutils/docutils/parsers/rst/__init__.py#l59
This is exactly what we're doing. I think it's okay that Docutils added the
init_customizations() method between versions -- it sounds like it was their
only option.
I don't have a strong sense yet how we want to reference GitHub issues (are
there any cases yet?) so it's hard to judge whether consistency between Jira
and GitHub is desirable. One thing I personally like about TS-1234 (for Jira)
is that we use the same in commit messages, source code comments, etc. so it's
consistent in that sense.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
