docs(readme): update README.md #331
Merged
Conversation
This file contains 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
lfkwtz
approved these changes
Aug 25, 2023
I have been facing a lot lot of issues due to a simple misunderstanding in the documentation, so I'm changing it in order to avoid having other people facing the same problem.
remarkablemark
force-pushed
the
modified-readme-file
branch
from
23afa30
to
8bf97d4
Compare
remarkablemark
approved these changes
Apr 1, 2024
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.
I have been facing an issue due to this misunderstanding for days. So I'm adding a comment in it to avoid having other people facing the same problem. Basically the functionality of "auto selecting" is implemented and working good, but on the README.md file it gives the other fellow programmers the idea that the attributes
valueanditemKeyare both doing it the same, only based in different attributes from theitems.That unfortunately isn't true, as stated on the issues #265 and possibly #311 . In order to solve my problem, the attribute
itemKeywas the one that worked, and notvalue(when inserting a state variable to thevalueattribute, on iOS it just keeps scrolling back to the first value of the variable, even when overwriting this value inside theonValueChange.While this issue is not yet solved, it's a good practice to stay transparent with other users that are using this library, and avoid this kind of confusion at any cost.