Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
More flexible data providers
See original GitHub issueThis component is helpful but it seems unnecessarily complicated to require users to create a service that implements AutoCompleteService when they may have an existing function in the parent component or another service with a name that is different from getResults.
Why not simply allow users to pass in any callback function
<ion-auto-complete [dataProvider]="mySearchFn" labelAttribute="name"></ion-auto-complete>
Where mySearchFn can be any function that accepts a string argument and returns an array?
Also, as I have in my above example, labelAttribute can be an @Input parameter of the component instead of making it a property of a service.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Yes I do. This would be much simpler to use by developers, who could then re-use existing functions in their component or other services without needing to have a special service just to use this component.
Fixed e78f12eedb0546d3dda6cd317127b84a1917aeb9