Skip to content

Conversation

@jirhiker
Copy link
Member

@jirhiker jirhiker commented Dec 4, 2025

Why

This PR addresses the following problem / context:

  • Use bullet points here

How

Implementation summary - the following was changed / added / removed:

  • Use bullet points here

Notes

Any special considerations, workarounds, or follow-up work to note?

  • ⚠️ 🚨 🦺 For safety, I changed the database port the testing suite uses. port=54321. Updated docker-compose.yml

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ 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".

@codecov-commenter
Copy link

codecov-commenter commented Dec 4, 2025

Codecov Report

❌ Patch coverage is 60.56338% with 28 lines in your changes missing coverage. Please review.
✅ All tests successful. No failed tests found.

Files with missing lines Patch % Lines
transfers/util.py 22.22% 28 Missing ⚠️
Files with missing lines Coverage Δ
db/thing.py 97.97% <100.00%> (-2.03%) ⬇️
schemas/thing.py 95.19% <100.00%> (-2.49%) ⬇️
services/util.py 61.46% <100.00%> (+4.54%) ⬆️
tests/__init__.py 100.00% <100.00%> (ø)
tests/conftest.py 86.29% <ø> (-7.14%) ⬇️
tests/test_geo_services.py 100.00% <100.00%> (ø)
tests/test_location.py 100.00% <ø> (ø)
tests/test_thing.py 66.49% <100.00%> (-33.51%) ⬇️
tests/test_transfer_legacy_dates.py 100.00% <100.00%> (ø)
transfers/util.py 22.46% <22.22%> (-4.21%) ⬇️

... and 20 files with indirect coverage changes

Copy link
Contributor

@jacob-a-brown jacob-a-brown left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Besides codex' comments about chunk_by_size I think that it looks good. I need to head out for the evening, and we are trying to get the transfer initiated tonight, so I'm approving it so it can be merged and transferred after codex' comments are addressed (whether changes need to be made or not)

jirhiker and others added 16 commits December 3, 2025 20:31
use SFC for all santa fe county organizations for standardized nomenclature
this was originally used and I removed it in the refactor. I added it
back to ensure validation errors are caught if an organization is not
in the lexicon
this is the nomenclature used by AMP and in the feature files, so
this change improves consistency across the codebase and teams
This field used to be standalone, but with the creation and implementation
of the polymorphic notes table it has been moved there
It used to be called "Other" but has been changed to "General"
The feature file requests specific note types. By returning all notes
at once, duplicate entries will be returned. Furthermore, some note
types only apply to specific thing types. So, general notes are
returned for all thing types, but then for each thing type specific
notes will be returned
Use consistent naming conventions for organizations in lexicon and data mapper.
jirhiker and others added 29 commits December 4, 2025 17:03
…tion-speed-of-welltransferer

Stream after-hook processing in WellTransferer
…sfer-and-updates

BDMS 233: notes transfer and updates
…es and refactor measuring point height validation
@jirhiker jirhiker merged commit 38f2d00 into staging Dec 6, 2025
5 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.

4 participants