script_name is the part of the path that matched current route, not the name of the script or the raw stuff from PSGI request.

I suggest route_name as this implies the value is a string rather than an object. Also, it emphasizes that it is the route and not the script.

path_info is anything that follows that matching part, for instance a wiki article name.

Even many years ago, I never liked path_info but it was the convention and I never thought of a better alternative. Even now, I'm not sure if there's a better name and it does fit with historical convention. Maybe route_params, but just params (or param) could be confusing. I'm not sure if there is a good enough alternative to justify not using the already familiar path_info (despite that I never liked the name).

Sometimes there are good reasons to not follow historical convention. Other times, not. Most cases, a minor change to convention is the better choice. Changing script_name to route_name falls under this 3rd category.

In reply to Re: Better names for SCRIPT_NAME/PATH_INFO in a web framework? by RonW
in thread Better names for SCRIPT_NAME/PATH_INFO in a web framework? by Dallaylaen

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.