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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

More efficient name completion data retrieval #4

Closed
Rexios80 opened this issue Nov 17, 2023 · 2 comments
Closed

More efficient name completion data retrieval #4

Rexios80 opened this issue Nov 17, 2023 · 2 comments

Comments

@Rexios80
Copy link
Owner

Rexios80 commented Nov 17, 2023

I'm thinking we have two options:

Store the package names in the Realtime Database during backend updates

Has the added benefit of only showing packages we have data for

Use the new optimized name completion endpoint

https://pub.dev/help/api#additional-apis
https://pub.dev/api/package-name-completion-data

Would need to PR pub_api_client to add this
Will not contain all packages we have data for (especially an issue if we use the suggestions to do things like adding to comparison)

@Rexios80
Copy link
Owner Author

Another thought is we could use the optimized name completion endpoint and just show the current query as the first option

@Rexios80
Copy link
Owner Author

That's what I ended up doing

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

No branches or pull requests

1 participant