refactor exchange error checking code #304
Merged
Conversation
This file contains 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
Owner
w7sst
commented
Apr 15, 2024
w7sst
commented
- move exchange error checking into separate procedures
- replace error strings with error codes
- error strings are now found in a table
- add TContest.FindQsoErrors to allow specialization by contest
- move exchange error checking into separate procedures - replace error strings with error codes - error strings are now found in a table - add TContest.FindQsoErrors to allow specialization by contest
|
I always like to do code movement (refactoring) in a separate checkin. This change combines code movement and rewrite since the error string assignments are now done using an error code and a table lookup. Otherwise the behavior should be the same. |
f6fvy
reviewed
Apr 15, 2024
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.