Skip to content

chore: return safe copy of string slice in 'ParseStringSliceClaim' #17439

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Apr 28, 2025

Conversation

Emyrk
Copy link
Member

@Emyrk Emyrk commented Apr 16, 2025

Claims parsed should be safe to mutate and filter. This was likely not causing any bugs or issues, and just doing this out of precaution

Claims parsed should be safe to mutate and filter. This was likely
not causing any bugs or issues, and just doing this out of precaution
@Emyrk Emyrk force-pushed the stevenmasley/idp_sync_safe_ref branch from eb80dca to 8494aa9 Compare April 17, 2025 14:48
Copy link
Member

@johnstcn johnstcn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TMTOWTDI but this is the fastest (ref: https://go.dev/wiki/SliceTricks#copy)

@Emyrk Emyrk merged commit 37c5e7c into main Apr 28, 2025
34 checks passed
@Emyrk Emyrk deleted the stevenmasley/idp_sync_safe_ref branch April 28, 2025 17:18
@github-actions github-actions bot locked and limited conversation to collaborators Apr 28, 2025
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