V1.0.0.1 release#249
Conversation
[BDMS-690 & BDMS-689]: Update the columns on the Wells list page to include contact info
Remove Field Event History component
- Move location info from CoreWellInfo to InteractiveSatelliteMap (renamed to Location) - Move elevation info from CoreWellInfo and WellSummaryBar to Physical Properties - Convert CoreWellInfo to compact 3-column stat bar (Hole Depth, Well Depth, Measuring Point) - Standardize ConstructionInfo, PhysicalProperties, and GeologyInformation to inline text style - Add site_name to IWell and surface it as Contacts card heading
- Update IWellDetails to replace removed fields with field_events list - Expand IFieldEvent with nested field_event_participants and contact types - Derive first visit participants from oldest field event (last in desc-sorted list) - Wire firstVisitParticipants into MonitoringInfoCard as First Visit Staff - Resolve merge conflict in well-show.tsx
…eld_events data Add nested sample/observation types to IFieldActivity and field_activities to IFieldEvent. Derive recentObservations (flattened from all field_events) and latestSample (from newest field event) in well-show, replacing the empty placeholder props previously passed to both components.
The paged field_events list (25 newest) does not include the oldest visit for wells with many field events. Consume the new first_field_event field returned by the API to reliably source first-visit participants regardless of history length. Also fixes participant contact name rendering: the API returns name/organization on ContactResponse, not contact_name/contact_organization.
…ent to their respective files
Reorganize card into two sections: status fields above the divider, visit history below. Add Last Visit Date from newest field event. Relabel duration as Measured For. Add bullet points to First Visit Staff list.
[BDMS-721]: Well Monitoring Card
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8bd53424c5
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| .flatMap((sample) => sample.observations ?? []) | ||
| .filter((obs) => obs.observation_datetime != null) |
There was a problem hiding this comment.
Restrict recent observations to water-level measurements
recentObservations is built from every sample observation that has a timestamp, so non-water-level measurements (for example chemistry observations) are now mixed into data later used by both RecentWaterLevelObservationsCard and WellPDFDownloadButton. For wells with mixed observation types, this causes the “Recent Water Level Observations” table and PDF summary fields to show irrelevant rows or blank depth values. Filter to groundwater-level observations (or at least rows with depth_to_water_bgs) before sorting.
Useful? React with 👍 / 👎.
| const newestEvent = fieldEvents[0] | ||
| if (!newestEvent) return undefined | ||
| const firstActivity = newestEvent.field_activities?.[0] | ||
| return firstActivity?.samples?.[0] ?? undefined |
There was a problem hiding this comment.
Compute latest sample across all event activities
latestSample currently assumes the newest sample is always fieldEvents[0] -> field_activities[0] -> samples[0], which is only correct if all three arrays are guaranteed ordered and non-empty. If the newest event’s first activity has no samples (or activities are ordered differently), the PDF loses/uses the wrong WL method even though valid recent samples exist elsewhere in the response. Select the latest sample by scanning all event activities and comparing sample/event dates.
Useful? React with 👍 / 👎.
Preview DeploymentPreview URL: https://preview-staging-auejgdbofq-uc.a.run.app Note: This preview uses the staging API endpoints. |
Preview DeploymentPreview URL: https://preview-staging-auejgdbofq-uc.a.run.app Note: This preview uses the staging API endpoints. |
1 similar comment
Preview DeploymentPreview URL: https://preview-staging-auejgdbofq-uc.a.run.app Note: This preview uses the staging API endpoints. |
Drive thing_id from React Query queryKey inside the hydrograph queryFn, forward AbortSignal through ocotillo getList and axios, show loading while the query is pending, and remount the chart when the well id changes. Add .cursor to gitignore for local Cursor metadata.
WellList passes name_contains (not query) so the staging API can filter by substring on Thing.name. ListPage accepts optional searchAriaLabel for screens that customize server-side search. Well list placeholder and aria text describe searching by well name instead of search all records.
NO TICKET: Update lock on sider logic
BDMS-763 Improve well attachments grid and file table.
BDMS-773 Fix hydrograph stale data when switching wells
Preview DeploymentPreview URL: https://preview-staging-auejgdbofq-uc.a.run.app Note: This preview uses the staging API endpoints. |
2 similar comments
Preview DeploymentPreview URL: https://preview-staging-auejgdbofq-uc.a.run.app Note: This preview uses the staging API endpoints. |
Preview DeploymentPreview URL: https://preview-staging-auejgdbofq-uc.a.run.app Note: This preview uses the staging API endpoints. |
BDMS-774 Wells list: name_contains search and filter UX labels
Preview DeploymentPreview URL: https://preview-staging-auejgdbofq-uc.a.run.app Note: This preview uses the staging API endpoints. |
…oved list updates
…gon-tool-on-map-doesn-t-update-the-list-on-right-side feat(map): filter features by selection polygons and update dependencies in effects
Preview DeploymentPreview URL: https://preview-staging-auejgdbofq-uc.a.run.app Note: This preview uses the staging API endpoints. |
V1.0.0.1 release of the UI