Skip to content

fix(performance): correct check for disabling performance #2595

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

Closed
wants to merge 1 commit into from

Conversation

Splaktar
Copy link
Contributor

Checklist

Description

  • if the app doesn't inject anything and the values are null,
    then we should enable instrumentation and data collection by default

Fixes #2502

Code sample

N/A

- if the app doesn't inject anything and the values are `null`,
  then we should enable instrumentation and data collection by default

Fixes angular#2502
@jamesdaniels
Copy link
Member

Sorry to miss your PR on this, was hacking on it at the same time :P

@Splaktar
Copy link
Contributor Author

No problem. I understand.

@Splaktar Splaktar deleted the fix-performance-enabling branch September 27, 2020 21:50
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.

enableProdMode stops AngularFirePerformanceModule?
3 participants