Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposed resolution of issue #157 and #149 #173

Closed
wants to merge 2 commits into from

Conversation

joaobertholino
Copy link
Contributor

@joaobertholino joaobertholino commented Nov 19, 2024

Fixing warnings regarding class mappings with Map Struct as per Pull Request #168 and from issue #157.
Implemented the use of ProblemDetail in error responses according to issue #149.

@joaobertholino joaobertholino changed the title Fixing warnings regarding class mappings with Map Struct Fixing warnings regarding class mappings with Map Struct (from issue #157) Nov 19, 2024
@joaobertholino joaobertholino changed the title Fixing warnings regarding class mappings with Map Struct (from issue #157) Fixing warnings regarding class mappings with Map Struct Nov 19, 2024
@joaobertholino joaobertholino changed the title Fixing warnings regarding class mappings with Map Struct Proposed resolution of issue #157 and #149 Nov 19, 2024
@@ -18,6 +20,7 @@ public interface OwnerMapper {

Owner toOwner(OwnerDto ownerDto);

@Mappings(value = {@Mapping(target = "id", ignore = true), @Mapping(target = "pets", ignore = true)})
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion: we could avoid the @Mappings annotation
See https://mapstruct.org/documentation/stable/reference/html/#basic-mappings

public ErrorInfo(Exception ex) {
this(ex.getClass().getName(), ex.getLocalizedMessage());
}
private ProblemDetail detailBuild(Exception ex, HttpStatus status) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion: could you please split your Pull Request into 2 PR?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants