new port-search wildcarding - bad idea?

* for an exact match use "quoting", a bit like what Google does
to enforce a search term

* otherwise terms are assumed to be wildcard bounded and case insensitive

* without quotes, * and ? characters are supported for multi and single
character wildcards.

we could revert this commit if we don't like it.
This commit is contained in:
Oliver Gorwits
2013-09-08 22:41:17 +01:00
parent e77a806f65
commit 947614ddd8
9 changed files with 24 additions and 14 deletions

View File

@@ -12,7 +12,7 @@
<tr>
<td>[% row.device.dns || row.device.ip | html_entity %]</td>
<td class="nd_center-cell"><a class="nd_linkcell"
href="[% device_ports %]&q=[% row.device.dns || row.device.ip | uri %]&f=[% row.port | uri %]&c_duplex=on">
href="[% device_ports %]&q=[% row.device.dns || row.device.ip | uri %]&f=%22[% row.port | uri %]%22&c_duplex=on">
[% row.port | html_entity %]</a></td>
<td class="nd_center-cell">[% row.name | html_entity %]</td>
<td class="nd_center-cell">[% row.duplex.ucfirst | html_entity %]</td>