Skip to content

Conversation

@nickvergessen
Copy link
Member

@nickvergessen nickvergessen commented Nov 27, 2025

Fix #284

Signed-off-by: Joas Schilling <coding@schilljs.com>
Signed-off-by: Joas Schilling <coding@schilljs.com>
@nickvergessen nickvergessen self-assigned this Nov 27, 2025
@nickvergessen nickvergessen added the bug Something isn't working label Nov 27, 2025
Copy link

@Antreesy Antreesy left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Member

@provokateurin provokateurin left a comment

Choose a reason for hiding this comment

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

I'm not sure if this is a good idea. Having the parameter marked as required, has the benefit, that consumers need to think about what they want. If it's not required but also has no default value, then it's easier to forget about the parameter.

I'm fine with merging, however it could lead to confusion in the opposite direction.

@nickvergessen
Copy link
Member Author

Having the parameter marked as required

… has the problem that typescript generated from it does not allow submitting the request without specifying the value in your client side code, which basically makes the idea of having a server defined default which we can change with an update not possible 🙈

@nickvergessen nickvergessen merged commit c631d38 into main Dec 2, 2025
22 checks passed
@nickvergessen nickvergessen deleted the bugfix/153/fix-optional-values branch December 2, 2025 08:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Params with default constant marked as required

4 participants