{"action":"opened","issue":{"url":"https://api.github.com/repos/api-platform/core/issues/2066","repository_url":"https://api.github.com/repos/api-platform/core","labels_url":"https://api.github.com/repos/api-platform/core/issues/2066/labels{/name}","comments_url":"https://api.github.com/repos/api-platform/core/issues/2066/comments","events_url":"https://api.github.com/repos/api-platform/core/issues/2066/events","html_url":"https://github.com/api-platform/core/issues/2066","id":338168668,"node_id":"MDU6SXNzdWUzMzgxNjg2Njg=","number":2066,"title":"Keys difference on JSON vs. JSON-LD","user":{"login":"er1z","id":1813302,"node_id":"MDQ6VXNlcjE4MTMzMDI=","avatar_url":"https://avatars2.githubusercontent.com/u/1813302?v=4","gravatar_id":"","url":"https://api.github.com/users/er1z","html_url":"https://github.com/er1z","followers_url":"https://api.github.com/users/er1z/followers","following_url":"https://api.github.com/users/er1z/following{/other_user}","gists_url":"https://api.github.com/users/er1z/gists{/gist_id}","starred_url":"https://api.github.com/users/er1z/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/er1z/subscriptions","organizations_url":"https://api.github.com/users/er1z/orgs","repos_url":"https://api.github.com/users/er1z/repos","events_url":"https://api.github.com/users/er1z/events{/privacy}","received_events_url":"https://api.github.com/users/er1z/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-07-04T07:58:22Z","updated_at":"2018-07-04T07:58:22Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"I have a data created by custom data provider. Using JSON-LD the data looks like this:\r\n\r\n```\r\n{\r\n  \"@context\": \"/api/contexts/Struct\",\r\n  \"@id\": \"/api/structs\",\r\n  \"@type\": \"hydra:Collection\",\r\n  \"hydra:member\": [\r\n    {\r\n      \"@id\": \"/api/structs/50c10eb8-ff18-4b02-9ca7-96c4efd78610\",\r\n      \"@type\": \"Struct\",\r\n      \"field1\": \"50c10eb8-ff18-4b02-9ca7-96c4efd78610\",\r\n      \"field2\": 1530690809\r\n    },\r\n    {\r\n      \"@id\": \"/api/structs/0f9f8409-08a7-4f52-bfa6-28bd91965ef0\",\r\n      \"@type\": \"Struct\",\r\n      \"field1\": \"0f9f8409-08a7-4f52-bfa6-28bd91965ef0\",\r\n      \"field2\": 1530690809\r\n    },\r\n    {\r\n      \"@id\": \"/api/structs/cf6e09ca-667e-4155-a7bd-c93369bedece\",\r\n      \"@type\": \"Struct\",\r\n      \"field1\": \"cf6e09ca-667e-4155-a7bd-c93369bedece\",\r\n      \"field2\": 1530690809\r\n    },\r\n    {\r\n      \"@id\": \"/api/structs/821920b5-bf87-474f-8d19-0ede22390b85\",\r\n      \"@type\": \"Struct\",\r\n      \"field1\": \"821920b5-bf87-474f-8d19-0ede22390b85\",\r\n      \"field2\": 1530690809\r\n    }\r\n  ],\r\n  \"hydra:totalItems\": 4\r\n}\r\n```\r\n\r\nWhereas using pure JSON produces:\r\n\r\n```\r\n{\r\n  \"1\": {\r\n    \"field1\": \"27557fc5-7f22-4c67-992e-da999f89e303\",\r\n    \"field2\": 1530690972\r\n  },\r\n  \"2\": {\r\n    \"field1\": \"488b08c4-3aee-41f1-89c3-72c258cae9f6\",\r\n    \"field2\": 1530690972\r\n  },\r\n  \"3\": {\r\n    \"field1\": \"61559539-2a52-491a-8518-e495fcc30c78\",\r\n    \"field2\": 1530690972\r\n  },\r\n  \"4\": {\r\n    \"field1\": \"6903a099-42cb-4bf1-ace2-11a2244ee029\",\r\n    \"field2\": 1530690972\r\n  }\r\n}\r\n```\r\n\r\nHow keys should look like? Implementing partial paginator enforces using iterator and yielding keys. Two questions:\r\n\r\n1. Which form is correct? Both with keys or neither?\r\n2. How to disable keys creation within pure JSON object and keep custom data provider with pagination?"}}
{"actor":{"display_login":"er1z"}}