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

[INV3777] Cache Wells for Offline Chemical Treatment use #3809

Merged
merged 16 commits into from
Jan 24, 2025

Conversation

LocalNewsTV
Copy link
Collaborator

@LocalNewsTV LocalNewsTV commented Jan 23, 2025

Overview

This PR includes the following proposed change(s):

  • Implement SQLite and LocalForage for caching Well Data
  • Well Repositories can be found by matching Bounding boxes or by ID
    • Future 'Plan my Trip' type functionality will let our caches share a common ID, but this is not that day.
  • Well Records are cached at the same time as Map tiles are cached, sharing a common bounding box
  • Well Records are deleted when Map tiles are deleted
  • Incoming wells filter out from existing wells reducing DB Transactions in subsequent areas
  • due to localforage constraints, well Ids are stored/gathered as strings and parsed on the way out.
  • Closes Cache Well Data for Offline #3777

Copy link

Quality Gate Failed Quality Gate failed

Failed conditions
0.0% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud

@plasticviking plasticviking merged commit 7e962ec into dev Jan 24, 2025
6 of 10 checks passed
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

Successfully merging this pull request may close these issues.

Cache Well Data for Offline
2 participants