Skip to content

[shared_preferences] Fix confusing language in README #8049

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.

Sign up for GitHub

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
auto-submit merged 4 commits into from
Nov 9, 2024
Merged

[shared_preferences] Fix confusing language in README #8049

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
d97a6fb
[shared_preferences] Fix confusing language in README
stuartmorgan-g Nov 8, 2024
f85551b
Version bump
stuartmorgan-g Nov 8, 2024
63c21d4
README
stuartmorgan-g Nov 8, 2024
e52f309
Clarify scope in legacy class doc comment
stuartmorgan-g Nov 8, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
[shared_preferences] Fix confusing language in README 
One use of "class" instead of "plugin" to refer to the `SharedPreferences` class specifically slipped through review. This updates it to make it clear that it's talking about a specific class, not the plugin.
  • Loading branch information
@stuartmorgan-g
stuartmorgan-g authored Nov 8, 2024
commit d97a6fb805809abdb0855b8315bf76bbe2604ed3
2 changes: 1 addition & 1 deletion packages/shared_preferences/shared_preferences/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -160,7 +160,7 @@ A tool to make this process easier can be tracked here: https://github.com/flutt

#### Adding, Removing, or changing prefixes on SharedPreferences

By default, the `SharedPreferences` plugin will only read (and write) preferences
By default, the `SharedPreferences` class will only read (and write) preferences
that begin with the prefix `flutter.`. This is all handled internally by the plugin
and does not require manually adding this prefix.

Expand Down