update outdated reference.log for resolved warnings #3417
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
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.
This PR updates the reference.log file for the package "DB" to remove outdated entries related to resolved warnings. The changes ensure the codebase remains clean and up-to-date.
fixes : #2758
Details:
The following outdated warnings were removed from the reference.log file:
match_dbcols: no visible binding for global variable '.'
match_dbcols: no visible binding for global variable 'as'
Undefined global functions or variables: . as
Suggestion to add importFrom("methods", "as")
Reason for Update:
The as function is already included in the NAMESPACE file via importFrom("methods", "as"), and the issue is resolved in the current codebase. The warnings in the reference.log are no longer valid.
Verification:
Ran rcmdcheck::rcmdcheck("path/to/package") to confirm that the package builds successfully with no errors, warnings, or notes.
Impact:
This PR ensures the reference.log file reflects the current state of the code and helps maintainers and contributors avoid confusion.