fix: LS26002468: forced strict equality check in row length - #2899
Merged
Conversation
zammarchi-smeup
requested review from
Leonardo-Signorelli,
lucafoscili and
pasere-smeup
as code owners
September 7, 2026 15:04
lucafoscili
approved these changes
Sep 7, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This pull request makes a small code style improvement in the
KupDataTablecomponent. The equality comparison in a condition is updated to use the strict equality operator for better type safety.kup-data-table.tsxfrom==to===to enforce strict type comparison in the row cell value reset logic.