-
Notifications
You must be signed in to change notification settings - Fork 581
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
separate header shortcuts from other accessors #1913
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Confirmed all headers in %NAMES have a
=head2
entry - Confirmed all
=head2
entries not in %NAMES are not header shortcuts... - ...except
referrer
andreferer
, as explained in the PR description, which do not make use of generated accessors
d213ff2
to
3d72f13
Compare
I will happily rebase this branch (and confirm that the changes are still accurate) if I can get this reviewed -- but I lack the permissions to tag the team for review. |
3d72f13
to
3dd1c60
Compare
Rebased! |
Pull request has been modified.
This pull request is now in conflicts. Could you fix it @karenetheridge? 🙏 |
3dd1c60
to
fbc99b4
Compare
This improves readability by making it easier to find the methods that aren't simply shortcuts to particular headers. I have confirmed that the headers listed in %NAMES exactly matches those in the pod, except for referer and referrer which have custom subs.
fbc99b4
to
fab6ab9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree 👍
thanks! |
This improves readability by making it easier to find the methods that aren't
simply shortcuts to particular headers.
I have confirmed that the headers listed in %NAMES exactly matches those in
the pod, except for referer and referrer which have custom subs.