Use lastObject instead of objectAtIndex:0 in multivalued section for row template #372
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
…emplate for new row. This is needed when you add values programmatically to a multivalued section. With objectAtIndex:0 the new row will contain the value of the first added row; which in normal circumstances works because you use a dummy row with a placeholder text. When adding rows programmatically based on predefined data this does not make sense.
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.
Be default use lastObject instead of objectAtIndex:0 in multivalued section as template for new rows. This is needed when you add values programmatically to a multivalued section. With objectAtIndex:0 the new row will contain the value of the first added row; which in normal circumstances works because you use a dummy row with a placeholder text. When adding rows programmatically based on predefined data this does not make sense.
It is possible avoid this using multivaluedRowTemplate on a form. The default behaviour is still nonsensical in my opinion.