Back to the channels

#java

06:53 deebo anyone happen to use spring-data-rest? is there some existing class in some spring library for deserializing json from the "weird" { "_embedded": { "resultTypes": [...] } response?
07:57 deebo -> config.useHalAsDefaultJsonMediaType(false) -> everyone started clapping
08:00 Para ~gpt summarize what jackson's config.useHalAsDefaultJsonMediaType means and what does it do in context of spring-data-rest, including what is "hal"
08:00 javabot In Spring Data REST, Jackson's `config.useHalAsDefaultJsonMediaType` is a configuration property that sets 'HAL' as the default media type for JSON responses. 'HAL' stands for Hypertext Application Language, a standard which structures API responses to contain not just data, but also hyperlinks for accessing related data. Using it helps to decouple client from server, easing the evolution of the RESTful API.
08:00 Para Sounds like SOAP but worse tbh.
08:01 deebo HATEOAS psychosis
08:02 Para Well, at least "hate" is built in...
08:02 deebo i just want to stop writing controller -> service -> repository crud, but spring-data-rest wants to produce something that's meant for 2005 i guess
08:03 deebo don't think i've ever seen a "real" rest/hateoas/whatever api in the wild
08:39 NeXeN deebo: consume the standard rest/hal api. shouldn't be writing custom json parsers. CollectionModel<T> would map directly to a collection response wrapped in _embedded, EntityModel<T> map to a single resource wrapped in hypermida links, then of course PageModel<T> maps pagged metadata like page, size, totalElements.
08:40 NeXeN you know instead of using basic http client or standard jackson mapping, WebClient or RestTemplate or traverson
08:43 NeXeN https://docs.spring.io/spring-hateoas/docs/current/reference/html/#client
08:43 javabot NeXeN's title: "Spring HATEOAS - Reference Documentation"
08:46 NeXeN i just feel like custom json parsers are an anti-pattern, *shrug*
08:50 NeXeN if you just want standard crud, spring mvc controllers are better imho
09:21 deebo .. its not custom anything? i'm just disabling the HAL/HATEOAS style response generation, so the responses area always plain application/json
09:21 deebo but it's anyhow looking like i need to ditch this, seems it's forcing GET usage for search apis, which means you hit the url size limit with very few params in our case
09:56 Para deebo: fwiw use idea's live templates :D
09:57 Para Write your get controller handle as parameterized live template, allow the intelligent autocomplete to produce gaps, fill the gaps, repeat for service/repo, write the actual bits which are missing.
12:30 deebo yeah already quickly wrote data-rest out, just have to find a generic way since all these repositories are just save + findById(s) + find(Pageable)