-
Notifications
You must be signed in to change notification settings - Fork 1
transfer #268
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
Conversation
keeping the organization mapping in a single file is easier for maintenance and to standardize names in Ocotillo since it'll enable quick comparisons
this uses the new single table rather than two tables that contain the same information
There was a problem hiding this 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 Report❌ Patch coverage is
|
jacob-a-brown
left a comment
There was a problem hiding this 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)
…g in water levels transfer
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
…water levels transfer
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.
… enhancing logging
…fault None handling
…nhance error logging
…ing in pre-commit config
…n transfer process
…n transfer process
…tion-speed-of-welltransferer Stream after-hook processing in WellTransferer
… in transfer process
…sfer-and-updates BDMS 233: notes transfer and updates
…and session management
…and add test cases
…est files for clarity
…es and refactor measuring point height validation
…handling in photo retrieval
Why
This PR addresses the following problem / context:
How
Implementation summary - the following was changed / added / removed:
Notes
Any special considerations, workarounds, or follow-up work to note?