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

Limit returnElements when searching for wellbores #2535

Open
eliasbruvik opened this issue Aug 29, 2024 · 0 comments
Open

Limit returnElements when searching for wellbores #2535

eliasbruvik opened this issue Aug 29, 2024 · 0 comments
Labels
Enhancement Improvement of existing functionality

Comments

@eliasbruvik
Copy link
Contributor

When you use the search bar to search for wellbores (both with and without wildcards), we currently fetch all wellbores with all data, and then filter it locally. We need to fetch all the wellbores in order to perform wildcard searches, but we should only request the information we need. In this case idOnly could be enough.

Select Wellbores from the dropdown to search for wellbores.
image

useGetWellboreSearch.ts or wellboreService.cs seems like the most relevant files. We currently re-use useGetWellbores with an empty string as the wellUid, which uses the wellbores endpoint to fetch all wellbores for all wells. Either pass along more information to the endpoint to decide what data to fetch, or see if it's enough to always use idOnly if we request wellbores without specifying the uids.

@eliasbruvik eliasbruvik added the Enhancement Improvement of existing functionality label Aug 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement Improvement of existing functionality
Projects
None yet
Development

No branches or pull requests

1 participant