Implement XML::LibXML::Element->appendTextNode
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 70/100
Research direction
Start in src/main/perl/lib/XML/LibXML.pm where the XML::LibXML::Element interface is defined, and compare with the neighbouring text/child methods already implemented there to see how nodes are represented. Mirror system XML::LibXML's appendTextNode semantics, then add a focused test (including the XML::LibXML::Ferry::create path) and run it under Perl, the JVM and interpreter backends. Done means the probe's can("appendTextNode") is true and t/ferry-write.t from Ferry v0.8.5 runs all 22 tests to completion.
Written by the indexing model from the issue text.
Description
Summary
XML::LibXML::Element in the bundled PerlOnJava compatibility implementation does not provide appendTextNode. Pure-Perl XML::LibXML::Ferry calls this method when creating an element with text, so XML-LibXML-Ferry v0.8.5 aborts in t/ferry-write.t on both PerlOnJava backends.
Reproduction
use XML::LibXML;
my $doc = XML::LibXML::Document->new('1.0', 'UTF-8');
my $element = $doc->createElement('Root');
$element->appendTextNode('text');
Under the PerlOnJava bundled XML::LibXML, this dies with:
Can't locate object method "appendTextNode" via package "XML::LibXML::Element"
The minimal Ferry trigger is:
use XML::LibXML::Ferry;
my $doc = XML::LibXML::Document->new('1.0', 'UTF-8');
my $root = $doc->createElement('Root');
$root->create('Child', 'text');
XML::LibXML::Ferry::create calls $el->appendTextNode($text) at its element-creation path. The bundled src/main/perl/lib/XML/LibXML.pm defines the XML::LibXML::Element interface but has no appendTextNode implementation. System XML::LibXML provides the method, as shown by the complete upstream suite passing under system Perl.
Evidence
- Distribution:
XML-LibXML-Ferryv0.8.5; CPAN run20261119-133823-51077. - PerlOnJava CPAN run:
t/ferry-write.texited 255 after 2 of 15 planned tests; remaining tests did not run becauseappendTextNodewas missing. - System Perl oracle: the full suite passed, 6 test programs and 22 tests, after installing
XML::LibXMLand its prerequisites in an isolated CPAN environment. - Focused API probe on PerlOnJava v5.44.1, source commit
94cc21a9c4e81e1c0fff4debf384efde2f758f93:can("appendTextNode")returned false on both the JVM and interpreter backends. - Runtime used for the probe: Temurin Java 24.0.2 on macOS arm64.
XML::LibXMLreverse-dependency lookup: 492 unique released runtime dependants, 85 with releases in the last five years. This is ecosystem context for the prerequisite; the target Ferry distribution itself is pure Perl.
Expected behavior
The bundled XML::LibXML::Element should support appendTextNode with behavior compatible with system XML::LibXML, so Ferry can create elements containing text and its write tests can run to completion on both backends.
Acceptance criteria
- Add the missing
XML::LibXML::Elementmethod in the shared bundled implementation, matching system XML::LibXML behavior. - Add focused project-owned coverage for appending text to an element, including the Ferry creation path.
- Verify the focused tests under standard Perl, PerlOnJava JVM, and PerlOnJava interpreter backends.
- Re-run
XML-LibXML-Ferryv0.8.5 tests and confirm all 22 tests pass under PerlOnJava.
- Dominant language
- Perl
- Stars
- 67
- Forks
- 8
- Avg merge
- 5h 12m
- Merged PRs (30d)
- 131
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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:parser bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
fglock/PerlOnJava#2137 ·
Maintainers usually reply within 1 day
-
area:backend area:cpan-port area:runtime bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
fglock/PerlOnJava#2071 ·
Maintainers usually reply within 1 day
-
area:runtime documentation enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
fglock/PerlOnJava#1579 ·
Maintainers usually reply within 1 day
-
area:cpan-port bug
Difficulty 3/5 1-2 days Newbie friendliness 62/100
fglock/PerlOnJava#2157 ·
Maintainers usually reply within 1 day
-
area:cpan-port area:parser area:runtime bug
Difficulty 3/5 1-2 days Newbie friendliness 66/100
fglock/PerlOnJava#2156 ·
Maintainers usually reply within 1 day
All issues in fglock/PerlOnJava
Similar issues
-
Dev-output directory preparation accepts file-valued lib/include paths and fails on dangling linksOpenteam-cli
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
Difficulty 1/5 Under an hour Newbie friendliness 93/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
inverse-inc/packetfence#9728 ·
Maintainers usually reply within 1 day
-
fix(char-create): show the real reason a character is refusedPossibly taken @baphomello claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day