Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add Immediate/ImmediateDelate to/in FluentAutocomplete #1951

Closed
Mike-E-angelo opened this issue Apr 26, 2024 · 1 comment 路 Fixed by #2052
Closed

feat: add Immediate/ImmediateDelate to/in FluentAutocomplete #1951

Mike-E-angelo opened this issue Apr 26, 2024 · 1 comment 路 Fixed by #2052
Assignees
Labels
status:needs-investigation Needs additional investigation
Milestone

Comments

@Mike-E-angelo
Copy link

馃檵 Feature Request

FluentAutocomplete does not have Immediate / ImmediateDelay properties. Because of this calls are being made to an api for each keypress and it's a bit chatty. 馃槉

馃 Expected Behavior

Less chatty API calls with each keypress

馃槸 Current Behavior

An API call with each keypress 馃槥

馃拋 Possible Solution

Implement Immediate/Delay as it is with FluentTextField which works perfectly. 馃檹

馃敠 Context

Attempting to reduce the amount of calls to API. 馃憤

馃捇 Examples

FluentTextField.Immediate and FluentTextField.ImmediateDelay works amazingly well. 馃檹 Thank you for any consideration!

@microsoft-github-policy-service microsoft-github-policy-service bot added the triage New issue. Needs to be looked at label Apr 26, 2024
@vnbaaij vnbaaij added status:needs-investigation Needs additional investigation and removed triage New issue. Needs to be looked at labels Apr 26, 2024
@vnbaaij vnbaaij added this to the v4.7.2 milestone Apr 26, 2024
@vnbaaij vnbaaij modified the milestones: v4.7.2, 4.7.3 May 4, 2024
@Mike-E-angelo
Copy link
Author

Wow thank you so much @vnbaaij! 馃檹

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:needs-investigation Needs additional investigation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants