We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Description/Screenshot The readme stat at one place the fetch collection is disabled by default and on an other place that it is active by default:
Setting Up Autocollection
Network Dependency Requests made by your app XHR and Fetch (fetch collection is disabled by default) requests, include information on
Configuration
disableFetchTracking | boolean | false | If true, Fetch requests are not autocollected. Default is false (Since v2.8.0, previously true)
I assume, that "fetch collection is disabled by default" has been not updated, when changing the default in 2.8.0
Steps to Reproduce
Expected behavior
No Contradiction about fetch in the documentation.
Additional context Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Correct, we need to update the documentation to indicate that it is now enabled by default (since 2.8.0)
Thank you.
Sorry, something went wrong.
fetch default value sync #2005 (#2010)
0c02d22
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
siyuniu-ms
No branches or pull requests
Description/Screenshot
The readme stat at one place the fetch collection is disabled by default and on an other place that it is active by default:
Setting Up Autocollection
Configuration
I assume, that "fetch collection is disabled by default" has been not updated, when changing the default in 2.8.0
Steps to Reproduce
Expected behavior
No Contradiction about fetch in the documentation.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: