Ronny Perinke

It is okay if this change (_sending HAL-formatted responses when accepting `application/json`_) is intended. But having set `spring.hateoas.use-hal-as-default-json-media-type=false` should not make the application unusable. So the question would be how...

Here is the sample application. [spring-boot-issue-26814.zip](https://github.com/spring-projects/spring-boot/files/6617036/spring-boot-issue-26814.zip) With Spring Boot 2.4.6 you can make a GET request such as http://localhost:8080/demo/foo with your browser and it will produce an response like this...

It is possible to register the default `ObjectMapper` for `application/json` using `WebFluxConfigurer.configureHttpMessageCodecs(ServerCodecConfigurer)` for type `org.springframework.hateoas.RepresentationModel`. But this is basically the same as if `spring.hateoas.use-hal-as-default-json-media-type` is set to `true`. That means:...

That's good news, thanks! I tried to mimic what Spring HATEOAS [WebfluxCodecCustomizer](https://github.com/spring-projects/spring-hateoas/blob/main/src/main/java/org/springframework/hateoas/config/WebfluxCodecCustomizer.java) would do if `withGenericJsonTypes` where `true`. @wilkinsona, would your approach be an option for `HypermediaAutoConfiguration` for the case...

My example with `PathMatcher` should show what _IMHO_ would be expected when using `isDirectoryContaining`. Right now you have to adjust the patterns to either include the parent directory or prepend...

Great, thank you.

### Workaround (Spring Based) Based on https://vaadin.com/docs/latest/flow/advanced/modifying-the-bootstrap-page/#IndexHtmlRequestListener-interface and https://vaadin.com/docs/latest/flow/advanced/service-init-listener a possible workaround could look like this. ```java @Bean VaadinServiceInitListener vaadinServiceInitListener() { return event -> { event.addIndexHtmlRequestListener(indexHtmlResponse -> { // workaround...

love to see this coming. Adding tags during BOM upload has been on the wish list for a while now (#586).

You can import the current swagger.json and convert it to openapi.yml using https://editor.swagger.io/, so you do not have to start from scratch. [This site](https://swagger.io/docs/specification/about/) is also a good starting point...

One approach would be to support some well-known versioning schemes such as Semver or Maven and add a property to each project that specifies the type of versioning used for...