Skip to content

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

Closed
Splaktar wants to merge 1 commit into
angular:masterfrom
DevIntent:fix-performance-enabling
Closed

Splaktar wants to merge 1 commit into
angular:masterfrom
DevIntent:fix-performance-enabling

Conversation

@Splaktar

Copy link
Copy Markdown
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
Copy Markdown
Contributor

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

@Splaktar

Copy link
Copy Markdown
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