Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Text::Markdown::Hoedown callback renderer lacks upstream setter methods

Ouverte
  • Quelque chose ne va pas ?
#1,522 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 2 jours

Personne n'a encore pris cette issue.

Évaluation

Difficulté
3/5
Temps estimé
1-2 jours
Accessibilité débutants
76/100
Type d'issue
Bug
Clarté
Clairement spécifiée
Activité
Active
Stack technique
java, perl
Domaine
backend, testing-qa

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

area:backend area:cpan-port bug

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->new
  • Text::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.

Langage dominant
Perl
Étoiles
64
Forks
6
Merge moyen
4 h 53 min
PR mergées (30 j)
165

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de fglock/PerlOnJava

Toutes les issues de fglock/PerlOnJava

Issues similaires

Plus d'issues Perl

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.