docs(MVUX): Introduce reader in how to use UpdateAllAsync for simple types like string #2927
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
There was a problem hiding this comment.
Pull Request Overview
This PR updates the ListStates.md documentation file to improve structure, clarity, and consistency. The changes focus on better organization of content, enhanced descriptions, and standardized method naming.
- Fixed formatting issues and removed malformed YAML front matter
- Enhanced documentation structure with improved headings and added tabbed sections
- Added new example demonstrating
UpdateAllAsyncwith simple types - Updated method names to match actual API (e.g.,
ClearSelection→ClearSelectionAsync)
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
16 tasks
…types like string as UpdateItemAsync is not available for string for example, this is at least telling the reader how to work at all in this situations chore: apply review suggestion Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> chore: apply review suggestion Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> chore: update naming leftover not renamed item chore: apply review suggestion Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> chore: apply reword suggestion
DevTKSS
force-pushed
the
docs-mvuxliststate-updateitemasync-is-not-possible-like-showed-in-the-docs-if-the-item-is-a-simple-string
branch
from
80dc189 to
fb7a61b
Compare
…nc-is-not-possible-like-showed-in-the-docs-if-the-item-is-a-simple-string
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
GitHub Issue (If applicable): closes #2881
PR Type
What kind of change does this PR introduce?
What is the current behavior?
The docs are not telling anything about how this could be done with non-record/complex types, so the assumption would normally be that it makes no change what the Action handles. But because simple types like string do not implement anything near
IKeyEquatable<T>this can and did result in the case a user did closely follow the docs but not got to any working/usable state of code in the app.What is the new behavior?
The reader is now told how to work with ListState Update actions when he might not have complex types like records then only a list of strings for example.
PR Checklist
Please check if your PR fulfills the following requirements:
Screenshots Compare Test Runresults.Other information
Internal Issue (If applicable):