feat: OSD: add detection and logging of multiline formatting in typical pedon#84
Merged
feat: OSD: add detection and logging of multiline formatting in typical pedon#84
Conversation
019db4b to
fc989af
Compare
bb68fff to
7cd2e0d
Compare
a00339d to
352f3b4
Compare
Member
Author
|
This PR reorders the horizon lines from typical pedon and resulting JSON output to match the order it was parsed so that the index position can be used to identify multiline statements within the typical pedon description. Currently we have some old-style O horizons that are only matching the "no bottom depth" horizon pattern, and thus have been sorting out of order for some time. Merging this and proceeding with another PR that will work on #85. The log output identifies 594 series across all regions with multiline issues in typical pedons: |
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
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.
For identifying the scope of #83