Search and Top Navigation
#6113 closed enhancement (worksforme)
Opened September 27, 2010 01:02PM UTC
Closed September 27, 2010 01:08PM UTC
Last modified October 11, 2012 09:15PM UTC
Custom query parameter
| Reported by: | AdeelEjaz | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | ui.autocomplete | Version: | 1.8.5 |
| Keywords: | autocomplete | Cc: | |
| Blocked by: | Blocking: |
Description
Hi,
The current implementation attaches a parameter called "term" which is hard-coded. This is not ideal when autocomplete is implemented in a system that already expects something like "q". Changing the backend to "term" might break other implementations that give out "q".
The best way to handle this is to allow an option to be passed called "param" or "queryParam", etc
You can already implement any system you want by passing a function as the source option. Check out the remote with cache demo to see an example.