Skip to content
Browse files

Autocomplete: Better explanation of URLs for source option. Fixes #58.

  • Loading branch information...
1 parent 21e4314 commit 81d9d7b985cadbe96fe79c2abc71f58c80c6acc0 @scottgonzalez scottgonzalez committed
Showing with 1 addition and 1 deletion.
  1. +1 −1 entries/autocomplete.xml
View
2 entries/autocomplete.xml
@@ -61,7 +61,7 @@
</desc>
</type>
<type name="String">
- <desc>When a string is used, the Autocomplete plugin expects that string to point to a URL resource that will return JSON data. It can be on the same host or on a different one (must provide JSONP). The Autocomplete plugin does not filter the results, instead the request parameter <code>term</code> gets added to the URL, which the server-side script should use for filtering the results. The data itself can be in the same format as the local data described above.</desc>
+ <desc>When a string is used, the Autocomplete plugin expects that string to point to a URL resource that will return JSON data. It can be on the same host or on a different one (must provide JSONP). The Autocomplete plugin does not filter the results, instead a query string is added with a <code>term</code> field, which the server-side script should use for filtering the results. For example, if the <code>source</code> option is set to <code>"http://example.com"</code> and the user types <code>foo</code>, a GET request would be made to <code>http://example.com?term=foo</code>. The data itself can be in the same format as the local data described above.</desc>
</type>
<type name="Function">
<argument name="request" type="Object"/>

1 comment on commit 81d9d7b

@timbotron

That is beautiful, thank you.

Please sign in to comment.
Something went wrong with that request. Please try again.