If you're closer to the Zurich area, you can see the talk at the local Java User Group on February, 4th.

Last but not least, the test suite is now much stronger as the relevant JSON marshalling is black-box tested.

If you're curious about the details, take a look at this PR 👇

github.com/spring-proje...

After the changes, how the extension communicates with Notion is fully an implementation detail, tailored to its scope and no longer exposed to users. All public types are now decorated with Jackson annotations, and there is no need for an intermediate layer to handle request & response conversion.

The HTTP Service Client really stands out for its brevity and ease of use. Plus, the versioning support introduced in Framework 7 is a perfect match for the Notion API.

Jackson doesn't really need any introduction, and I lost track of how many times I wondered, "Can I really do this with Jackson?!"

Notion recently deprecated the database endpoints that Spring Batch Notion indirectly uses, and a new pattern should be adopted. Unfortunately, the maintainer has no bandwidth for this, so I've taken the opportunity to rewrite what is needed with the Spring HTTP Service Client and Jackson 3.

• It offers a larger API surface than Spring Batch Notion requires, available to users transitively
• It pulls Kotlin and Gson as transitive dependencies
• It can slow down the adoption of new Notion API types and versions
• Browsing its sources from Java is challenging, like with any Kotlin library

Thanks a lot, Ted! 🙏

Many thanks to you, @mcpringle.bsky.social, and Alexandra, for the amazing organization! 🙏

So many new contributors to @assertj.github.io in a single day!

github.com/hack-commit-...