Fix Issue with generating the in1.txt of a problem #174 #175
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
…nd improve input handling in findSample function fix(parse.go): ensure input is cleaned before writing to files to prevent unwanted HTML tags in output
…oved readability and maintainability
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 pull request addresses issue #174, which involved unwanted HTML tags appearing in the generated
in1.txtfiles.Changes include:
stripHTMLTagsFunction: This function removes HTML tags from the input content, ensuring clean text output.findSample: The function now cleans the input before writing it to the files, preventing HTML tags from being included in the output.These improvements ensure that the content of
in1.txtis clean and properly formatted, resolving the reported issue.