Fix well integrity parsing#125
Open
TheRealDougSchmidt wants to merge 3 commits into
Open
Conversation
Also added WellIntegrityPanel.razor to improve the display of well integrity activities
DelayedAppender was modified to merge WellIntegrity records from the same visit. Unlike other DTOs, the WellIntegrity DTO is just a collection of other well-related activity, with no real defining properties. The bug fix avoids 3 repair records on the same day creating 3 well integrity records with one repair each. Now it will create a single well integrity record with 3 repair activities.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
@ChrisKanaganayagam-AI @AlvinLee-AI I'm back from vacation, quickly cobbled up the remaining the
WellIntegrityCSV and TOML example, and promptly found a bug!This PR adds the example files and fixes the discovered bug.
I also noticed a couple of deployment quirks that someone at AquaticInformatics will need to fix, since I don't have project rights anymore.
Fix the published release version in the AppVeyor project
25.4and reset the next counter to0That should publish the next build of the plugin as
v25.4.0instead ofv21.4.14, which aligns better with the expected plugin version naming patter. A plugin version of25.4.ximplies that the plugin will be compatible with AQTS 2025.4-or-higher.Manually deploy the updated Blazor TestDrive project to GitHub pages
The previous version of the plugin from 4 years ago is still deployed at https://aquaticinformatics.github.io/tabular-field-data-plugin/test-drive/ so nobody can test the new functionality.
Someone with project admin rights will need to do this after the PR is merged:
masterbranch locallydocs/publish-test-drive.shto publish the updated test drive project to GitHub PagesCheers!