You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@johnzon.apache.org by "Romain Manni-Bucau (JIRA)" <ji...@apache.org> on 2017/09/25 02:46:00 UTC

[jira] [Commented] (JOHNZON-136) Review @JohnzonIgnoreNested

    [ https://issues.apache.org/jira/browse/JOHNZON-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178462#comment-16178462 ] 

Romain Manni-Bucau commented on JOHNZON-136:
--------------------------------------------

Think we still need it to

1. Work ootb without overhead
2. Cases where you dont care about the ref or cant deserialize them properly like custom exceptions

Wdyt?

> Review @JohnzonIgnoreNested
> ---------------------------
>
>                 Key: JOHNZON-136
>                 URL: https://issues.apache.org/jira/browse/JOHNZON-136
>             Project: Johnzon
>          Issue Type: Bug
>          Components: Mapper
>    Affects Versions: 1.1.3
>            Reporter: Mark Struberg
>             Fix For: 1.1.4
>
>
> With the introduction of using JsonPointers for cyclic references we do not need @JohnzonIgnoreNested anymore imo.
> Should we deprecate it?
> Or do we keep it and fix the test to show a real use case?
> The only situation where it now makes sense is if a nested object contains attributes which I do not want to serialise.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)