- Notifications
You must be signed in to change notification settings - Fork618
feat: sanitize release names upon submission#2725
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:main
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Uh oh!
There was an error while loading.Please reload this page.
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
Uh oh!
There was an error while loading.Please reload this page.
@JacobCoffee is there an issue associated with this PR? I mean it makes sense but hard to say if it is "correct" without some documenting reason. |
yeah sorry, i thought if i put it in the commit message it would link it |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
I would recommend using aValidator rather than overriding clean.
Uh oh!
There was an error while loading.Please reload this page.
JacobCoffee commentedMay 6, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
doh... before i do all the migrations and things, do you think overriding the name on the NameSlugModel and adding the validator is still the best path@ewdurbin? I'm okay with either just wanting to make sure |
Uh oh!
There was an error while loading.Please reload this page.
Description
Closes#2724