-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handling non-array response from endpoint? #17
Comments
hi @lentzi |
…f results is an object and associated with a key Added @input() taEmptyOnSelect to empty the field on result selection
Is there a current status on this?
Where does the
Is the library intended to be extensible? |
@i-n-g-m-a-r i'm thinking about a proper handler for this |
@orizens maybe something like this: Client component:
NgxTypeAheadComponent:
|
It’s a great idea, my application query result from Solr and it can only return in object form. Any plan to fix this? |
Does the component only work if the request returns an array? My endpoint returns an object in the form of { statusCode: "200", entity: Array[] }. Is there a way to tell the component to handle response.entity instead of response, because currently I'm getting an error when the component tries calling response.map() when response is actually an object. (I've looked through all your public resources, including the demo)
The text was updated successfully, but these errors were encountered: