Skip to content

refactor: use strings.ReplaceAll#293

Merged
tenthirtyam merged 1 commit intomainfrom
refactor/use-strings.ReplaceAll
Apr 28, 2025
Merged

refactor: use strings.ReplaceAll#293
tenthirtyam merged 1 commit intomainfrom
refactor/use-strings.ReplaceAll

Conversation

@tenthirtyam
Copy link
Copy Markdown
Collaborator

Refactors to use strings.ReplaceAll as it more clearly expresses the intent to replace all occurrences of the substring and is the idiomatic Go approach for this use case since Go 1.12.

@tenthirtyam tenthirtyam added this to the v1.1.1 milestone Apr 28, 2025
@tenthirtyam tenthirtyam requested a review from a team as a code owner April 28, 2025 00:24
@tenthirtyam tenthirtyam self-assigned this Apr 28, 2025
`strings.ReplaceAll` more clearly expresses the intent to replace all occurrences of the substring and is the idiomatic Go approach for this use case since Go 1.12.

Signed-off-by: Ryan Johnson <ryan.johnson@broadcom.com>
@tenthirtyam tenthirtyam force-pushed the refactor/use-strings.ReplaceAll branch from 890af16 to 4cde746 Compare April 28, 2025 00:25
@tenthirtyam tenthirtyam merged commit c68d78e into main Apr 28, 2025
14 checks passed
@tenthirtyam tenthirtyam deleted the refactor/use-strings.ReplaceAll branch April 28, 2025 16:16
@github-actions
Copy link
Copy Markdown

I'm going to lock this pull request because it has been closed for 30 days. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 30, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants