Skip to content

Conversation

@GuusLieben
Copy link
Member

@GuusLieben GuusLieben commented Aug 2, 2025

Type of Change

  • Enhancement (non-breaking change that affects existing code)
  • Feature (non-breaking change that adds functionality)

Description

basic-hello-world-java

A basic Hartshorn application implementing a 'Hello World' greeter using dependency injection. Showcasing application starters, configurations, property values, and loggers.

basic-hello-world-kotlin

Same application as basic-hello-world-java, but written in Kotlin.

application-observability

A small application showcasing the use of lifecycle observers.

application-processing

Sample application showcasing component pre- and post-processors, as well as binder post-processors. Also showcases activators as a small aspect of the application.

application-proxies

Showcase application to show both programmatic and declarative approaches to defining proxy behaviors.

application-reporting

Small application showcasing reporting capabilities. Includes a custom reporter, as well as a report collector and serializer.

Checklist

  • I have performed a self-review of my own code
  • I have added tests that prove it is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Related issue number is linked in pull request title
  • I have added documentation that describes my changes
  • Any dependent changes have been merged and published in downstream modules
  • I have rebased my branch on top of the latest develop branch

Related Issue

Closes #1125

…trict behavior

Strictness describes how a lookup should perform. Thus, if a request is
strict, the content of a collection should strictly match. A similar
rule is applied for non-strict (loose) requests. This left the question
as to when a collection should be created; when there are no elements?
Instead of making assumptions, this differentiates requests (indicated
by the presence of a strict/loose setting) from registrations (undefined
strict/loose setting).
…, fix incorrect existing toString implementations
@GuusLieben GuusLieben force-pushed the feature/##1125-sample-projects branch from b70dac0 to b8fc28a Compare August 10, 2025 10:21
@GuusLieben GuusLieben force-pushed the feature/##1125-sample-projects branch from ef207e9 to 4cc0b6a Compare August 10, 2025 11:03
@GuusLieben GuusLieben self-assigned this Aug 10, 2025
@GuusLieben GuusLieben added this to the 0.7.0 milestone Aug 10, 2025
@GuusLieben GuusLieben merged commit 2a7253f into develop/0.7.0 Aug 10, 2025
9 checks passed
@GuusLieben GuusLieben deleted the feature/##1125-sample-projects branch August 10, 2025 11:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

Add additional sample projects

2 participants