Pod::Weaver::Section::Collect should gather up and include any existing section of the same name

[karenetheridge]

I've got this in my weaver.ini:

[Collect / TYPES]
command = type

and this in my pod:

=head1 DESCRIPTION

...

=head1 TYPES

Multiple types are available, blah blah blah...

=type Foo

...

=type Bar

...

Which results in this woven pod:

=head1 DESCRIPTION

...

=head1 TYPES

=head2 Foo

...

=head2 Bar

...

=head1 TYPES

Multiple types are available, blah blah blah...

Is it possible to combine the existing 'TYPES' section in the original with the generated =head1 TYPES section?

I'd patch, but I don't know where to start.

[rjbs]

• Karen Etheridge notifications@github.com [2013-12-19T19:30:34]

  Is it possible to combine the existing 'TYPES' section in the original with the generated =head1 TYPES section?

I have meant to include this behavior from the start, but I knew I could get by without it indefinitely, and was just waiting for some sucker to offer to write a patch.

I'd patch, but I don't know where to start.

Did I say sucker? I meant hero.

The new "=head1 TYPES" is created by this code:

my $container = Pod::Elemental::Element::Nested->new({
  command => $self->header_command,
  content => $self->header,
});

$self->__used_container($container);

You should make that code first look for any existing element like that (Pod::Elemental::Selectors may help?) and remove it from the document, making it the container instead.

Be considerate of what happens if it has children already.

rjbs

[rjbs]

fixed by #28!

[karenetheridge]

@wchristian my hero!