Add documentation for new features of Flutter SDK v3 #33530
+56
−31
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Preview links (active after the
|
brett0000FF
approved these changes
Dec 22, 2025
Contributor
brett0000FF
left a comment
brett0000FF
left a comment
There was a problem hiding this comment.
Thanks for the update! Left a suggestion to fix a couple typos + a general suggestion for a future iteration. 🚀
content/en/real_user_monitoring/application_monitoring/flutter/setup.md
Outdated
Show resolved
Hide resolved
content/en/real_user_monitoring/application_monitoring/flutter/advanced_configuration.md
Outdated
Show resolved
Hide resolved
|
|
||
| To ensure the safety of your data, you must use a client token. For more information about setting up a client token, see the [Client Token documentation][3]. | ||
|
|
||
| ### Step 2 - Instrument your application |
Contributor
There was a problem hiding this comment.
Just some thoughts after reading this that we could apply in a future iteration:
- The Flutter Web support/limitations block sits between the Step 2 intro and the per-platform sections, which makes it harder to visually connect “Instrument” → “Platform requirements.” Could we move that content into the Web subsection (e.g., “Web requirements” + “Web limitations”)?
- The iOS/Android/Web sections would be easier to scan if they followed a consistent structure, such as:
- Requirements
- Where to configure
- Example
- Moving these sections into tabs could save on vertical space too.
Sharing for future cleanup—no need to address as part of this PR!
Co-authored-by: Brett Blue <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do? What is the motivation?
Flutter v3 will be out soon and contains a few new features and restrictions. Add documentation for the new version.
Merge instructions
Not ready for merge until v3 is released.
Merge readiness: