Skip to content
This repository has been archived by the owner on May 29, 2019. It is now read-only.

feat(typeahead): Support for a typeahead-should-select function #5794

Closed
wants to merge 1 commit into from

Conversation

christor
Copy link

By default behaves as before. If specified, allows a custom function
to be defined to determine whether the keydown event should trigger
selection

Closes #5671

}
});
}
break;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No need for break;

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

True...what was there before had a break; at the end of each case, so I followed suit with the default case. I'll remove it.

@deeg
Copy link
Contributor

deeg commented Apr 12, 2016

Before this could get merged it would need docs added for the new attribute.

@christor
Copy link
Author

Ah, good point. I'll look into adding that now.

@christor
Copy link
Author

Any thoughts on the name of the option? Does it fit with the others?

@wesleycho
Copy link
Contributor

I think typeahead-should-select would be a better name - thoughts?

@deeg
Copy link
Contributor

deeg commented Apr 18, 2016

@wesleycho, that sounds good to me! @christor, let us know if you have any outstanding questions to get this finished.

@christor
Copy link
Author

No, no more questions...just keep getting busy :-) typeahead-should-select works for me. I'll probably have time later this week to return to this.

@christor
Copy link
Author

christor commented May 3, 2016

@deeg, updated with suggestions and basic documentation

@christor
Copy link
Author

@deeg, @wesleycho: please let me know if you would like any more changes to this.

@christor christor changed the title feat(typeahead): Support for a typeahead-is-select-trigger function feat(typeahead): Support for a typeahead-should-select function May 11, 2016
@christor
Copy link
Author

@deeg , @wesleycho : Just following up to see if there's more work to be done here (don't mean to be a pest). Thanks.

@deeg
Copy link
Contributor

deeg commented May 17, 2016

@christor, could you please squash this down to one commit?

By default behaves as before. If specified, allows a custom function
to be defined to determine whether the keydown event should trigger
selection.

Closes angular-ui#5671
@christor
Copy link
Author

@deeg All squashed up. Let me know if you need something more. Thanks.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants