Merge a dependabot PR is probably not sufficient but the implementation needs to be tweaked to match the 1.2.x codebase.

https://docs.github.com/en/github/administering-a-repository/configuration-options-for-dependency-updates

• Labels
• Schedule
• Directory
• Assignees
• Reviewers

Remember to format and add comments and hint to documentation.

• No complex representations possible if not using the experimental feature
• No complete support for links/affordances

Is it possible that you could publish your project to Maven Central?

https://shields.io/ should be our friend.
https://blog.softwaremill.com/maven-badges-the-app-5c1bdcceca29 explains how to do it.

Merge a dependabot PR is probably not sufficient but the implementation needs to be tweaked to match the 1.1.1 codebase.

Need to check if some part of the AffordanceModel contains the value of the member variable that is part of the payload class. Class SirenLinkConverter needs to be enhanced.

Check the HalForms Mediatype implementation to adapt the features that were introduced in Spring HATEOAS version 1.3.

#40

@gregturn I would like to understand how a custom mediatype should provide an AffordanceModelFactory implementation? I'm currently using a spring.factories file and declare a org.springframework.hateoas.mediatype.AffordanceModelFactory entry referencing the Siren related factory class.

It works but is it also the way to go?

We need to find a way to be able to deserialize complex Siren Entity structures.
The currently implemented experimental feature is probably not the way to go (see spring-projects/spring-hateoas#1297).
Maybe some Siren related annotations like @SirenProperties, @SirenEntities etc is the way to go?!

Vulnerabilities

DepShield reports that this application's usage of com.google.guava:guava:21.0 results in the following vulnerability(s):

• (CVSS 5.9) [CVE-2018-10237] Deserialization of Untrusted Data

_{This is an automated GitHub Issue created by Sonatype DepShield. Details on managing GitHub Apps, including DepShield, are available for personal and organization accounts. Please submit questions or feedback about DepShield to the Sonatype DepShield Community.}

We currently enable the Siren hypermedia type as soon as the library is available on the classpath. But it is the only way until spring-projects/spring-hateoas#1304 is solved.

Related issues:

• spring-projects/spring-hateoas#1265
• spring-projects/spring-hateoas#1060

Check the comments of the mentioned issues as well to understand how to integrate the custom mediatype (how about spring.factories, HypermediaMappingInformation, MediaTypeConfigurationProvider?).

The project could not be analyzed because of build errors. Please review the error messages here. Another build will be scheduled within 24 hours. If the build is successful this issue will be closed, otherwise the error message will be updated.

_{This is an automated GitHub Issue created by Sonatype DepShield. GitHub Apps, including DepShield, can be managed from the Developer settings of the repository administrators.}

Mainly based on some feedback from some nice buddies!

https://github.com/kevinswiber/siren#type-2 explains the details.
Should be possible if spring-projects/spring-hateoas#1087 is solved.
Information seems to be available through the Spring HATEOAS version 1.3.0 release.

To be able to define complex Siren Entity structures.

Take a peek at toedter/spring-hateoas-jsonapi#2, for an initial view of moving off that unnecessary interface.

@toedter is working to polish the ACTUAL solution, so stay tuned.