You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since Micronaut 4 the default way to define application configuration is the property file format, which allowed removing the YAML dependencies from Micronaut projects. It is however easier to define the configuration in the YAML format.
It would be nice if Micronaut allowed defining application configuration in YAML and automatically convert it to the property file when building/packaging the application (e.g. using the Micronaut AOT plugin). This wouldn't support loading YAML at runtime but makes defining the application configuration easier (the generated YAML could include a comment describing this limitation).
One aspect to consider is whether or not this should be enabled by default. In my opinion this would improve the developer experience when creating new projects.
The text was updated successfully, but these errors were encountered:
If you import snakeyaml into your pom then it will load application.yml automatically.
I know. As of Micronaut 4 snakeyaml isn't added by default, I suppose in order to make the resulting application a bit leaner. For developer experience it would be nice to support yaml at build time without having the runtime dependency on snakeyaml
Feature description
Since Micronaut 4 the default way to define application configuration is the property file format, which allowed removing the YAML dependencies from Micronaut projects. It is however easier to define the configuration in the YAML format.
It would be nice if Micronaut allowed defining application configuration in YAML and automatically convert it to the property file when building/packaging the application (e.g. using the Micronaut AOT plugin). This wouldn't support loading YAML at runtime but makes defining the application configuration easier (the generated YAML could include a comment describing this limitation).
One aspect to consider is whether or not this should be enabled by default. In my opinion this would improve the developer experience when creating new projects.
The text was updated successfully, but these errors were encountered: