fix: apply "cannot_add_rows" directly to table field for more efficient solution (backport #44157) #44177
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
![mergify[bot]](https://avatars.githubusercontent.com/in/10562?s=60&v=4){kind=small}
…ld (optimized approach) (cherry picked from commit 5dd8eaf)
|
🎉 This PR is included in version 14.77.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
Problem:
The initial fix in PR #44148 to disable the "Add Row" button was not the most efficient approach.
Solution:
This update applies the
cannot_add_rowsproperty directly to the allocations table field, offering a cleaner and more efficient solution. It works the same as expected as in PR #44148 but with a more efficient code structure.This is an automatic backport of pull request #44157 done by [Mergify](https://mergify.com).