Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

RT Ticket #148: reparse parameter #14

Open
phinjensen opened this issue Mar 25, 2013 · 0 comments
Open

RT Ticket #148: reparse parameter #14

phinjensen opened this issue Mar 25, 2013 · 0 comments

Comments

@phinjensen
Copy link
Contributor

Created: Tue Dec 18 13:59:36 2007
Owner: Stefan Hornburg
Requestors: Kevin Walsh


Several of the tags list the reparse parameter even though the tags
don't return anything. The reparse parameter is pointless if the tag
will never return a value, so there's no point in listing the parameter
in this case.

A few examples:

write-relative-file, set, seti, tmp, tmpn, set-cookie

There are a lot more, but basically reparse is only a viable option if
the tag is designed to return a value.

Non-container tags use interpolate instead of reparse to control whether
or not the output is parsed.

Even that rule isn't complete: there are tags, such as [area], that
return a value that will never be affected by the reparse/interpolate
parameter.

Sticking with [area] for a moment. The [area] tag says:

interpolate = interpolate input?

reparse = reparse output?

  1. there is no input, as [area] is not a container tag.
  2. the output is unaffected by reparse (and by interpolate for that matter).
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant