Skip to content

docs: fix object spread typing and mis-named variables #1188

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

Merged
merged 1 commit into from
Oct 3, 2017
Merged

docs: fix object spread typing and mis-named variables #1188

merged 1 commit into from
Oct 3, 2017

Conversation

markgoho
Copy link
Contributor

@markgoho markgoho commented Oct 3, 2017

There was an issue with typing (I think) using the current way of returning a new object with the doc.id included. This method ensures that what gets returned is properly typed.

This method was used on two other examples (.stateChanges() and auditTrail()) so those were updated as well. I also found a handful of mis-named types (assume they were missed from copy/pasting) and so I updated those as well.

Checklist

  • Issue number for this PR: docs: map function error #1187
  • Docs included?: n/a
  • Test units included?: n/a
  • In a clean directory, npm install, npm run build, and npm test run successfully? yes

Description

Code sample

There was an issue with typing (I think) using the current way of returning a new object with the doc.id included. This method ensures that what gets returned is properly typed.

This method was used on two other examples (`.stateChanges()` and `auditTrail()`) so those were updated as well. I also found a handful of mis-named types (assume they were missed from copy/pasting) and so I updated those as well.
@davideast davideast merged commit f067dbd into angular:master Oct 3, 2017
@davideast
Copy link
Collaborator

Thank you @markgoho!

@markgoho markgoho deleted the patch-2 branch October 5, 2017 02:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants