Text::Markdown::Hoedown callback renderer lacks upstream setter methods
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 76/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- backend, testing-qa
Research direction
Start with the Java-backed Text::Markdown::Hoedown::Renderer::Callback replacement and the Perl compatibility module's AUTOLOAD path. Run the unchanged upstream t/03_custom.t with jperl and jperl --interpreter; done means callback setters such as doc_header are accepted and the test reaches done_testing() with the expected complete rendered output.
Written by the indexing model from the issue text.
Description
Summary
The PerlOnJava compatibility implementation of Text::Markdown::Hoedown 1.03 does not preserve the upstream callback-renderer API. The upstream custom-renderer test aborts when calling the first callback setter, doc_header.
CPAN reproduction
CPAN random-tester run: 20260925-091055-87943
Distribution: Text-Markdown-Hoedown-1.03
System Perl passes the complete upstream suite:
Files=4, Tests=12
Result: PASS
PerlOnJava reports:
Files=4, Tests=11
Result: FAIL
Failed 1/4 test programs. 0/11 subtests failed.
The test program that fails is the upstream t/03_custom.t callback-renderer test. The other three test programs (t/00_compile.t, t/01_simple.t, and t/02_toc.t) pass.
Reproduction
The failure reproduces on both execution backends:
jperl t/03_custom.t
jperl --interpreter t/03_custom.t
ok 1
# Tests were run but no plan was declared and done_testing() was not seen.
Can't locate object method "doc_header" via package
"Text::Markdown::Hoedown::Renderer::Callback"
The exception occurs at the upstream test's first callback registration:
my $cb = Text::Markdown::Hoedown::Renderer::Callback->new();
$cb->doc_header(sub { ... });
Cause
The original distribution is an XS/native binding, but PerlOnJava has an explicit Java replacement over commonmark-java. The replacement registers:
Text::Markdown::Hoedown::Renderer::Callback->newText::Markdown::Hoedown::Renderer::Callback->DESTROY
It does not preserve the callback setter methods expected by the upstream API. The Perl compatibility module defines an AUTOLOAD setter that stores each callback in the renderer object, but the Java-backed package dispatch currently does not reach that setter for doc_header (and therefore the other callback names).
The Java renderer later looks up callback names such as doc_header, doc_footer, normal_text, entity, header, codespan, paragraph, autolink, linebreak, underline, raw_html, image, link, footnote_ref, and footnote_def. The callback object must accept and retain all of these upstream setter calls.
The missing hoedown/test/MarkdownTest_1.0.3 fixture warnings and the native compiler probe warning during Build.PL are not the test failure: the relevant PerlOnJava Java replacement loads, and the failure is a deterministic method-dispatch/API-compatibility error in t/03_custom.t.
Impact
Reverse-dependency metadata reports 7 unique released runtime dependents and 2 recent dependents for Text::Markdown::Hoedown. Representative distributions include Web-API-Mock, Story-Interact-WWW, Qgoda, MySQL-Admin, Dancer2-Plugin-MarkdownFilesToHTML, and APISchema.
Suggested fix and regression coverage
Preserve the upstream callback setter surface on the Java-backed Renderer::Callback class. A suitable implementation can either make the Perl AUTOLOAD path reachable for unregistered callback methods or explicitly register compatible setter dispatch for the callback names.
Keep the unchanged upstream t/03_custom.t as the regression test and require it to pass on both JVM and interpreter backends. The test should reach done_testing() and retain the expected complete rendered output.
- Dominant language
- Perl
- Stars
- 64
- Forks
- 6
- Avg merge
- 4h 42m
- Merged PRs (30d)
- 170
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from fglock/PerlOnJava
-
area:cpan-port area:unicode bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
fglock/PerlOnJava#1341 ·
Maintainers usually reply within 2 days
-
area:backend area:cpan-port area:parser area:runtime bug
Difficulty 3/5 1-2 days Newbie friendliness 78/100
fglock/PerlOnJava#1528 ·
Maintainers usually reply within 2 days
-
Difficulty 3/5 1-2 days Newbie friendliness 74/100
fglock/PerlOnJava#1524 ·
Maintainers usually reply within 2 days
-
area:backend area:runtime bug
Difficulty 4/5 3-5 days Newbie friendliness 65/100
fglock/PerlOnJava#1523 ·
Maintainers usually reply within 2 days
-
area:backend area:io area:unicode bug
Difficulty 4/5 3-5 days Newbie friendliness 52/100
fglock/PerlOnJava#1520 ·
Maintainers usually reply within 2 days
All issues in fglock/PerlOnJava
Similar issues
-
Bug Priority
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
canonical/chisel-releases#1235 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
linuxmuster/sophomorix4#190 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
documentation Needs Triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
trizen/youtube-viewer#456 ·