Skip to content

fix: Prevent lowercase when sluggify #123

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 2 commits into from
May 29, 2025
Merged

fix: Prevent lowercase when sluggify #123

merged 2 commits into from
May 29, 2025

Conversation

alexluong
Copy link
Collaborator

resolves #122

@@ -180,6 +180,7 @@ func createSource(sdkClient *hookdeckclient.Client, name *string) (*hookdecksdk.
sourceName = answers.Label
}

slug.Lowercase = false
Copy link
Collaborator

Choose a reason for hiding this comment

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

@alexluong - any chance this has any side effects elsewhere? For example, does it set Lowercase globally, and if slug is used in some other file/function then the Lowercase setting will be set as true?

Ultimately, I'm assuming we only really want to use the function in Lowercase, but if we do I think we should have a utility function of our own to make it clear that the Lowercase is intended.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@leggetter great catch! So this will introduce a side effect, but this is the only place we use slug.

Ultimately, I'm assuming we only really want to use the function in Lowercase, but if we do I think we should have a utility function of our own to make it clear that the Lowercase is intended.

Done.

@leggetter leggetter merged commit 213a30b into main May 29, 2025
5 checks passed
@leggetter leggetter deleted the 122 branch May 29, 2025 16:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Investigate resource_already_exists error when passing --cli-path
3 participants