-
Notifications
You must be signed in to change notification settings - Fork 0
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
Optional error messages for constraints #1082
Labels
Comments
lars-reimann
pushed a commit
that referenced
this issue
Jan 4, 2025
## [0.23.0](v0.22.0...v0.23.0) (2025-01-04) ### Features * categorize API elements ([#1285](#1285)) ([3275900](3275900)), closes [#1243](#1243) * optional error messages for constraints ([#1275](#1275)) ([fce761c](fce761c)), closes [#1082](#1082) * prevent editing built-in stubs ([#1282](#1282)) ([d02c30a](d02c30a)) * show placeholders in outline ([#1286](#1286)) ([3880bfe](3880bfe)) ### Bug Fixes * subtype check for literal and union types ([#1288](#1288)) ([911881c](911881c)) * subtype check for literal and union types (part 2) ([#1289](#1289)) ([56284cf](56284cf)) * type inference for lambdas and their parameters ([#1304](#1304)) ([a9e070f](a9e070f))
🎉 This issue has been resolved in version 0.23.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem?
All constraints currently have a standard error message. It would be nice to be able to customize this
Desired solution
New syntax:
The message must evaluate to some constant string if we know parameter values. This would also allow template strings that reference the parameter value.
Possible alternatives (optional)
No response
Screenshots (optional)
No response
Additional Context (optional)
No response
The text was updated successfully, but these errors were encountered: