{"action":"created","issue":{"url":"https://api.github.com/repos/adjohnson916/jackson-json-reference/issues/15","labels_url":"https://api.github.com/repos/adjohnson916/jackson-json-reference/issues/15/labels{/name}","comments_url":"https://api.github.com/repos/adjohnson916/jackson-json-reference/issues/15/comments","events_url":"https://api.github.com/repos/adjohnson916/jackson-json-reference/issues/15/events","html_url":"https://github.com/adjohnson916/jackson-json-reference/pull/15","id":116150764,"number":15,"title":"Additional functionality  and yaml support","user":{"login":"slavaschmidt","id":322297,"avatar_url":"https://avatars.githubusercontent.com/u/322297?v=3","gravatar_id":"","url":"https://api.github.com/users/slavaschmidt","html_url":"https://github.com/slavaschmidt","followers_url":"https://api.github.com/users/slavaschmidt/followers","following_url":"https://api.github.com/users/slavaschmidt/following{/other_user}","gists_url":"https://api.github.com/users/slavaschmidt/gists{/gist_id}","starred_url":"https://api.github.com/users/slavaschmidt/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/slavaschmidt/subscriptions","organizations_url":"https://api.github.com/users/slavaschmidt/orgs","repos_url":"https://api.github.com/users/slavaschmidt/repos","events_url":"https://api.github.com/users/slavaschmidt/events{/privacy}","received_events_url":"https://api.github.com/users/slavaschmidt/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/adjohnson916/jackson-json-reference/labels/bug","name":"bug","color":"fc2929"},{"url":"https://api.github.com/repos/adjohnson916/jackson-json-reference/labels/enhancement","name":"enhancement","color":"84b6eb"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":13,"created_at":"2015-11-10T16:58:31Z","updated_at":"2015-11-22T20:10:55Z","closed_at":"2015-11-12T11:58:58Z","pull_request":{"url":"https://api.github.com/repos/adjohnson916/jackson-json-reference/pulls/15","html_url":"https://github.com/adjohnson916/jackson-json-reference/pull/15","diff_url":"https://github.com/adjohnson916/jackson-json-reference/pull/15.diff","patch_url":"https://github.com/adjohnson916/jackson-json-reference/pull/15.patch"},"body":"Thanks for looking into it!"},"comment":{"url":"https://api.github.com/repos/adjohnson916/jackson-json-reference/issues/comments/158794397","html_url":"https://github.com/adjohnson916/jackson-json-reference/pull/15#issuecomment-158794397","issue_url":"https://api.github.com/repos/adjohnson916/jackson-json-reference/issues/15","id":158794397,"user":{"login":"adjohnson916","id":615381,"avatar_url":"https://avatars.githubusercontent.com/u/615381?v=3","gravatar_id":"","url":"https://api.github.com/users/adjohnson916","html_url":"https://github.com/adjohnson916","followers_url":"https://api.github.com/users/adjohnson916/followers","following_url":"https://api.github.com/users/adjohnson916/following{/other_user}","gists_url":"https://api.github.com/users/adjohnson916/gists{/gist_id}","starred_url":"https://api.github.com/users/adjohnson916/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/adjohnson916/subscriptions","organizations_url":"https://api.github.com/users/adjohnson916/orgs","repos_url":"https://api.github.com/users/adjohnson916/repos","events_url":"https://api.github.com/users/adjohnson916/events{/privacy}","received_events_url":"https://api.github.com/users/adjohnson916/received_events","type":"User","site_admin":false},"created_at":"2015-11-22T20:10:55Z","updated_at":"2015-11-22T20:10:55Z","body":"@slavaschmidt Nice. In slavaschmidt@f9faa96, looks like you'll need to specify a `JsonReferenceProcessor#maxDepth`, maybe `10`, since the default of `1` won't cover that deeply nested reference.\r\n\r\nWhich makes me wonder, do you think we should have a `maxDepth` by default? Should it be greater than `1`? I feel if it were too great, then all typical use cases would pass, and users would end up with unanticipated bugs in production. Or we could not limit it at all by default, but would this cause unanticipated stack overflows in production? Expecting users to define explicitly might prevent confusion.\r\n"}}