1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
|
Description: Fixes manpage-has-errors-from-man
Origin: vendor
Forwarded: no
Author: Alessandro Ghedini <ghedo@debian.org>
Reviewed-by: gregor herrmann <gregoa@debian.org>
Last-Update: 2018-06-23
--- a/lib/Moose/Manual/Attributes.pod
+++ b/lib/Moose/Manual/Attributes.pod
@@ -645,7 +645,7 @@
However, we recommend that you use L<Moose::Meta::Attribute::Native> traits
for these types of attributes, which gives you much more control over how
they are accessed and manipulated. See also
-L<Moose::Manual::BestPractices#Use_Moose::Meta::Attribute::Native_traits_instead_of_auto_deref>.
+L<Moose::Manual::BestPractices/"Use Moose::Meta::Attribute::Native traits instead of auto deref">.
=head2 Initializer
--- a/lib/Moose/Cookbook/Meta/Labeled_AttributeTrait.pod
+++ b/lib/Moose/Cookbook/Meta/Labeled_AttributeTrait.pod
@@ -172,8 +172,8 @@
When you pass a metaclass to C<has>, it will take the name you provide and
prefix it with C<Moose::Meta::Attribute::Custom::Trait::>. Then it calls
C<register_implementation> in the package. In this case, that means Moose ends
-up calling
-C<Moose::Meta::Attribute::Custom::Trait::Labeled::register_implementation>.
+up calling C<register_implementation> from
+C<Moose::Meta::Attribute::Custom::Trait::Labeled>.
If this function exists, it should return the I<real> trait's package
name. This is exactly what our code does, returning
|
