A Fix Script to Scan and check for the log statements #160
Conversation
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
…og, gs.debug etc. in production environment which is against the best practices. The Fix script 'Scan for log statements' returns the line numbers where such statements have been used. The script is scalable and can be used to scan any table, or add any statement type in future.
SapphicFire
requested changes
Oct 22, 2024
There was a problem hiding this comment.
Thank you for your contribution. However, this submission is not relevant to this repository. We encourage contributors to review the project's objectives and guidelines (see the README.md and CONTRIBUTING.md files) before submitting pull requests. Closing this for now. Once you make additional changes, feel free to re-open this Pull Request or create a new one.
This is not an Instance Scan
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.
The script detects various log statements that should not be used in a production environment, such as gs.log, gs.debug, and others. It returns the line numbers where such statements are found. This allows you to scan scripts in any table, whether it’s in a background script, script include, or other areas. The script is robust and scalable, enabling you to scan any table by simply providing the table name and sys_id. Ensure that the correct backend field name for the script (e.g., script field) is specified. The array of log statements can be easily customized to include or exclude specific log types. The result is an array of line numbers where the specified log statements are used.