#fluent-api — Public Fediverse posts

“It compiles. It runs. But why doesn’t the JSP page update?” Fluent setters are tempting—but in legacy stacks, they can cause subtle, hard-to-find bugs.

Sergei Chernov’s guide helps weigh the risk—before prod breaks: https://javapro.io/2025/10/01/fluent-setter-breaking-the-convention/

#CleanCode #FluentAPI #LegacyCode

“It compiles. It runs. But why doesn’t the JSP page update?” Fluent setters are tempting—but in legacy stacks, they can cause subtle, hard-to-find bugs.

Sergei Chernov’s guide helps weigh the risk—before prod breaks: https://javapro.io/2025/10/01/fluent-setter-breaking-the-convention/

#CleanCode #FluentAPI #LegacyCode

Fluent setters reduce boilerplate, reveal object hierarchies, & simplify nested DTOs. But can they play nicely with inheritance? And what does the JavaBeans spec actually allow?

A deep dive into real code by Sergei Chernov: https://javapro.io/2025/10/01/fluent-setter-breaking-the-convention/

#CleanCode #FluentAPI #Lombok

Fluent setters reduce boilerplate, reveal object hierarchies, & simplify nested DTOs. But can they play nicely with inheritance? And what does the JavaBeans spec actually allow?

A deep dive into real code by Sergei Chernov: https://javapro.io/2025/10/01/fluent-setter-breaking-the-convention/

#CleanCode #FluentAPI #Lombok

Want to use fluent setters in DTOs? #Spring Boot, Jackson & MapStruct support them. But java.beans.Introspector, JSP tags & legacy EE apps may silently fail.

Sergei Chernov maps the compatibility landscape. Read before refactoring: https://javapro.io/2025/10/01/fluent-setter-breaking-the-convention/

#CleanCode #FluentAPI

Want to use fluent setters in DTOs? #Spring Boot, Jackson & MapStruct support them. But java.beans.Introspector, JSP tags & legacy EE apps may silently fail.

Sergei Chernov maps the compatibility landscape. Read before refactoring: https://javapro.io/2025/10/01/fluent-setter-breaking-the-convention/

#CleanCode #FluentAPI

Is returning this from a setter harmless—or a silent bug? Fluent setters promise clean code, but can break conventions in #Java beans.Introspector, Commons-BeanUtils & more.

Sergei Chernov shows where they break & shine: https://javapro.io/2025/10/01/fluent-setter-breaking-the-convention/

#SpringBoot #CleanCode #FluentAPI

Is returning this from a setter harmless—or a silent bug? Fluent setters promise clean code, but can break conventions in #Java beans.Introspector, Commons-BeanUtils & more.

Sergei Chernov shows where they break & shine: https://javapro.io/2025/10/01/fluent-setter-breaking-the-convention/

#SpringBoot #CleanCode #FluentAPI

🚨MAJOR RELEASE ALERT 🚨
Today we are launching BESSER v.4, with some massive improvements 👏🥳🎉:
✅ Project management: create new #modeling projects comprising different types of diagrams (#classdiagram, #statemachine, #objectdiagram...) in our #online #modeling #editor
✅Create object diagrams to model specific scenarios conforming to your class diagram
✅ #Evaluate #ocl constraints on your object diagram and get #feedback on whether your scenarios are #valid
✅ Plus many other improvements: #fluentapi, #rdf generation,...
📜https://github.com/BESSER-PEARL/BESSER/releases
⚙️https://github.com/BESSER-PEARL/BESSER

I can feel your #FOMO so don't wait any longer. Give it a try NOW ➡️ https://editor.besser-pearl.org/

Pls also reshare this post and drop a ⭐ on #github so that others can also benefit from our #opensource #lowcode #free #platform
#uml #ocl #classdiagram #database #sql #codegenerator #vibemodeling

🚨Announcement🚨

A new, version (2.1.0) of FluentContracts is LIVE!

We have brand new contracts available for "FileInfo", "DirectoryInfo", "Dictionary" and more!

Go, check it out!

Pls share 🙏

#dotnet #fluentapi

https://github.com/FluentContracts/FluentContracts

🚨Announcement🚨

A new, version (2.1.0) of FluentContracts is LIVE!

We have brand new contracts available for "FileInfo", "DirectoryInfo", "Dictionary" and more!

Go, check it out!

Pls share 🙏

#dotnet #fluentapi

https://github.com/FluentContracts/FluentContracts

🚨 Announcement 🚨

A new, major version (2.0.0) of FluentContracts is LIVE!

Some refactoring + some new cool contracts:

- String.BeCreditCardNumber
- String.BeBase64
- DateTime.BeInThePast/Future
- DateTime.BeWeekend

Pls share🙏

#dotnet #FluentAPI

https://github.com/FluentContracts/FluentContracts

🚨 Announcement 🚨

A new, major version (2.0.0) of FluentContracts is LIVE!

Some refactoring + some new cool contracts:

- String.BeCreditCardNumber
- String.BeBase64
- DateTime.BeInThePast/Future
- DateTime.BeWeekend

Pls share🙏

#dotnet #FluentAPI

https://github.com/FluentContracts/FluentContracts

🚨 Announcement 🚨

FluentContracts v1.4.0 has been released!
https://github.com/FluentContracts/FluentContracts/releases/tag/1.4.0

This version includes cool new "string" contracts like:
- BeEmailAddress (kudos to @dotnet) - BeIpAddress
- BeAlphanumeric

... and more!
And I am just getting started. Tons of others are in the making.
#dotnet #fluentapi

🚨 Announcement 🚨

FluentContracts v1.4.0 has been released!
https://github.com/FluentContracts/FluentContracts/releases/tag/1.4.0

This version includes cool new "string" contracts like:
- BeEmailAddress (kudos to @dotnet) - BeIpAddress
- BeAlphanumeric

... and more!
And I am just getting started. Tons of others are in the making.
#dotnet #fluentapi

🔧🔨 Builder Design Pattern in .NET C# 🚨

A step by step guide to develop a Fluent API from scratch in .NET C# using the Builder Design Pattern.

In this article, we would walk through the whole process of developing a Fluent API using the Builder Design Pattern, from the early steps of thinking about it, to the latest of testing it.

⁉️ What is the Builder Design Pattern?

It is a creational design pattern which allows creating complex objects into small simple steps one by one.

⁉️ What are the advantages of the Builder Design Pattern?

Some of the well-known advantages of the Builder Design Pattern are...

For the step by step guide, read the article below 👇

However, before jumping to the article, consider subscribing to the newsletter to get useful content delivered directly to your inbox 😀

📭 https://developmentsimplyput.com/subscribe

Builder Design Pattern in .NET C#

https://developmentsimplyput.com/post/builder-design-pattern-in-net-c

#dotnet #csharp #designpatterns #builder #fluentapi

🔧🔨 Builder Design Pattern in .NET C# 🚨

A step by step guide to develop a Fluent API from scratch in .NET C# using the Builder Design Pattern.

In this article, we would walk through the whole process of developing a Fluent API using the Builder Design Pattern, from the early steps of thinking about it, to the latest of testing it.

⁉️ What is the Builder Design Pattern?

It is a creational design pattern which allows creating complex objects into small simple steps one by one.

⁉️ What are the advantages of the Builder Design Pattern?

Some of the well-known advantages of the Builder Design Pattern are...

For the step by step guide, read the article below 👇

However, before jumping to the article, consider subscribing to the newsletter to get useful content delivered directly to your inbox 😀

📭 https://developmentsimplyput.com/subscribe

Builder Design Pattern in .NET C#

https://developmentsimplyput.com/post/builder-design-pattern-in-net-c

#dotnet #csharp #designpatterns #builder #fluentapi

🔧🔨 Builder Design Pattern in .NET C# 🚨

A step by step guide to develop a Fluent API from scratch in .NET C# using the Builder Design Pattern.

In this article, we would walk through the whole process of developing a Fluent API using the Builder Design Pattern, from the early steps of thinking about it, to the latest of testing it.

Builder Design Pattern in .NET C#

https://developmentsimplyput.com/post/builder-design-pattern-in-net-c

📭 https://developmentsimplyput.com/subscribe

#dotnet #csharp #designpatterns #builder #fluentapi

🔧🔨 Builder Design Pattern in .NET C# 🚨

A step by step guide to develop a Fluent API from scratch in .NET C# using the Builder Design Pattern.

In this article, we would walk through the whole process of developing a Fluent API using the Builder Design Pattern, from the early steps of thinking about it, to the latest of testing it.

Builder Design Pattern in .NET C#

https://developmentsimplyput.com/post/builder-design-pattern-in-net-c

📭 https://developmentsimplyput.com/subscribe

#dotnet #csharp #designpatterns #builder #fluentapi

A new #bot framework is born 🤖 👶 - Say 👋 to the new #BESSER Bot Framework:

- #OpenSource

- With an embedded #NLP Engine

- Tested with 🇫🇷 🇩🇪 🇪🇸 cat 🇺🇸 and partial support for 🇱🇺

- #Python-based with a #FluentAPI to hide the complexities of creating bots

- With #StateMachine semantics to create all types of bots

- #Intent-based to avoid hallucinations. Add #LLM support for those questions the bot is not #trained on

Read more ➡️ https://livablesoftware.com/besser-bot-framework/

Try it ➡️ https://github.com/BESSER-PEARL/BESSER-Bot-Framework 🧰

A new #bot framework is born 🤖 👶 - Say 👋 to the new #BESSER Bot Framework:

- #OpenSource

- With an embedded #NLP Engine

- Tested with 🇫🇷 🇩🇪 🇪🇸 cat 🇺🇸 and partial support for 🇱🇺

- #Python-based with a #FluentAPI to hide the complexities of creating bots

- With #StateMachine semantics to create all types of bots

- #Intent-based to avoid hallucinations. Add #LLM support for those questions the bot is not #trained on

Read more ➡️ https://livablesoftware.com/besser-bot-framework/

Try it ➡️ https://github.com/BESSER-PEARL/BESSER-Bot-Framework 🧰

@synlogic @ghorwood
For #Java, I would replace the last one with

"3. expert/never-hipster: uses jOOQ"

When I discovered #jOOQ years ago, it was eye-opening. One can really get the same level of control as with hand-written #SQL bit still have a comfortable API! Its author @lukaseder says that the guiding principle for designing this #FluentAPI is that jOOQ *is* SQL.

See the comparison image in this post: https://foojay.social/@foojay/110067514875132847

@synlogic @ghorwood
For #Java, I would replace the last one with

"3. expert/never-hipster: uses jOOQ"

When I discovered #jOOQ years ago, it was eye-opening. One can really get the same level of control as with hand-written #SQL bit still have a comfortable API! Its author @lukaseder says that the guiding principle for designing this #FluentAPI is that jOOQ *is* SQL.

See the comparison image in this post: https://foojay.social/@foojay/110067514875132847