diff options
| author | http://lj.rossia.org/users/imz/ <http://lj.rossia.org/users/imz/@web> | 2009-05-18 15:30:27 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2009-05-18 15:30:27 -0400 |
| commit | 8f1d02decf81f9f3d1214516927a134339dc6eeb (patch) | |
| tree | ea5e38c097c103be5b069812008df3b46e20dbbe | |
| parent | a4ce0468f6f562ad4ec749f156528aa5b3f2fe39 (diff) | |
minor: formatting.
| -rw-r--r-- | doc/bugs/pagespec_can__39__t_match___123__curly__125___braces.mdwn | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/bugs/pagespec_can__39__t_match___123__curly__125___braces.mdwn b/doc/bugs/pagespec_can__39__t_match___123__curly__125___braces.mdwn index e3146d92a..2f215d297 100644 --- a/doc/bugs/pagespec_can__39__t_match___123__curly__125___braces.mdwn +++ b/doc/bugs/pagespec_can__39__t_match___123__curly__125___braces.mdwn @@ -29,9 +29,11 @@ More tests: > curlies when doing so to avoid one being used to break out of the `q{}`. > > Alternative ways to handle it would be: +> > * Escape curlies. But then you have to deal with backslashes > in the user's input as they could try to defeat your escaping. > Gets tricky. +> > * Avoid exposing user input to interpolation as a string. One > way that comes to mind is to have a local string lookup hash, > and insert each user specified string into it, then use the hash |