René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Proposal: Optionally return a document ID on valueChanges()","articleBody":"A major pain point with angularfire continues to be mapping a document ID to a collection query. I propose we add an optional `withId` argument to `collection.valueChanges()`. This can be a simple non-breaking change and I can PR it. \r\n\r\n```js\r\ncollection.valueChanges(withId?: string)\r\n\r\n// emits [ { myIdKey: 'MrfFpRBfWLTd7LqiTt9u', ...data }, ... ]\r\n```\r\n\r\nThis will greatly simplify the code below\r\n\r\n```js\r\n// current requirement\r\nref.snapshotChanges()\r\n      .pipe(\r\n        map(actions =\u003e {\r\n          return actions.map(a =\u003e {\r\n            const data = a.payload.doc.data();\r\n            const id = a.payload.doc.id;\r\n            return { myIdKey: id, ...data };\r\n          });\r\n})\r\n\r\n// after change \r\n\r\nref.valueChanges('myIDKey')\r\n```","author":{"url":"https://github.com/codediodeio","@type":"Person","name":"codediodeio"},"datePublished":"2018-12-14T23:11:39.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":4},"url":"https://github.com/1973/angularfire/issues/1973"}