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
"Type-safe" is a confusing name #10
Comments
Hi @vprudnikov, thanks for opening the issue. I agree that, judging from this Twitter thread (and the various documentation links contained in it), it seems like the community has settled on using "Staged" for the name of this concept. I'll add |
@skinny85 , thanks for the response! Although I admit that I maybe asked it a wrong question :) |
@vprudnikov This is now done on the If everything looks good, I'll include these changes in the next release, that will also contain fixes for #5 and #11. |
@skinny85 , looks great! Thanks! |
This has been fixed in the latest Jilt release ( I'm closing this issue as "Resolved", please comment if you run into any more problems related to this area, and I'll reopen the issue. |
Hi!
Could you please consider renaming a "type-safe" builder to something else like "step builder" or "fluent builder"?
I'm asking about this since the "type-safe builder" is a bit confusing and usually means something different like https://kotlinlang.org/docs/type-safe-builders.html
More links:
So, while all the concepts may seem overlapping, "type-safe builder" is a broader term encompassing any builder pattern that uses the type system to enhance safety. In contrast "step builder" is a specific implementation style within the builder pattern.
The text was updated successfully, but these errors were encountered: