I released version 2.1.1 of JSON:API for Spring HATEOAS, see https://github.com/toedter/spring-hateoas-jsonapi/. This is a patch release, based on Spring Boot 3.4.0 and Spring HATEOAS 2.4.0.
I released version 2.1.0 of JSON:API for Spring HATEOAS, see https://github.com/toedter/spring-hateoas-jsonapi/. This is a feature release, based on Spring Boot 3.3.2 and Spring HATEOAS 2.3.1.
I released version 2.0.8 of JSON:API for Spring HATEOAS, see https://github.com/toedter/spring-hateoas-jsonapi/. This is a patch release, based on Spring Boot 3.3.1 and Spring HATEOAS 2.3.0.
Excited to welcome Panagiotis Moutsopoulos to #DrupalDevDays
Join Panagiotis at #DDD24 to explore #Drupal's philosophy of using a single module for most cases, presenting problems and their solutions with various core or contrib modules and technologies, including #Panels, #Context, #DisplaySuite, #LayoutBuilder, #REST, and #JSONAPI.
Learn more about the BoF session at https://ddd2024.drupalcamp.bg/drupal-dev-days-2024/session/drupals-alternate-realities
Please stop building Wild West JSON APIs.
The JSON:API specification exists, is a trivial amount more effort to implement, and makes using a Web API sooo much easier.
I did a decontextualised data journalism/vizualisation of online self and some fun animation to it up
https://chris.bur.gs/unreliable-narrator/
so many buzzwords bingoed
#eleventy #jsonapi #basicauth #fetch #drupal #migrate #dataviz? #animation #emoji #tinydata #bigdata
kiddo is challenging me to do new animations and speculating about how current ones math out
I released version 2.0.7 of JSON:API for Spring HATEOAS, see https://github.com/toedter/spring-hateoas-jsonapi/ This is a bug fix release, based on Spring Boot 3.2.1 and Spring HATEOAS 2.2.0.
@jandudulski different questions if you mean #jsonapi or #json #api
I like graphiti for jsonapi.
I hate #JSONAPI. It’s the worst standard ever invented.
I released version 2.0.6 of JSON:API for Spring HATEOAS, see https://github.com/toedter/spring-hateoas-jsonapi/. This is a maintenance release, based on Spring Boot 3.1.4 and Spring HATEOAS 2.1.2.
I'm really confused as to why this is so novel to those who comment here. #JSON was not even a part of #REST: it is usually not *representing* anything and is *not* self-explanatory. Clients somehow have to catch up to API changes all the time, and backend can go chill??? This must be an obvious flaw with #JSONAPI.
And yet, the concept of #hypermedia responses, that #HTMX and #HATEOAS try to remind us of, seems alien to most. Oof, now that's the power of gaslighting in development circles!
I released version 2.0.5 of JSON:API for Spring HATEOAS, see https://github.com/toedter/spring-hateoas-jsonapi/…. This is a maintenance release, based on Spring Boot 3.1.0 and Spring HATEOAS 2.1.0.
The #jsonapi specification allows a client requesting inclusion of related resources. And it supports heterogeneous collections containing resources of different types. Both features does not play very well together yet. I drafted a proposal to close the gap: https://github.com/json-api/json-api/issues/1695 Looking for feedback. Both from implementers of the spec as well as consumers working with the spec. Especially those using heterogeneous collections.
I released version 2.0.4 of JSON:API for Spring HATEOAS, see https://github.com/toedter/spring-hateoas-jsonapi/.
This is a bug-fix release, based on Spring Boot 3.0.4.
I released the new version 2.0.3 of JSON:API for Spring HATEOAS, see https://github.com/toedter/spring-hateoas-jsonapi/.
This is a bug-fix release, based on Spring Boot 3.0.4.
I released the new version 2.0.2 of JSON:API for Spring HATEOAS, see https://github.com/toedter/spring-hateoas-jsonapi/.
This is a bug-fix release, based on Spring Boot 3.0.2.