Skip to content

Conversation

@suresh-gangumalla
Copy link
Collaborator

Observed that while using computed property as for-loop data collection then for-loop effect is not tracking for all the other instance variables which are using in computed property function defintion. Ideally changes to any property inside computed function should execute for-loop again, This PR will actually collect list of those component refferences inside each computed method and track for-loop for all those component variables.

Observed that while using computed property as for-loop data collection
then for-loop effect is not tracking for all the other instance
variables which are using in computed property function defintion.
Ideally changes to any property inside computed function should execute
for-loop again, This PR will actually collect list of those component
refferences inside each computed method and track for-loop for all those
component variables.

Signed-off-by: Suresh Kumar Gangumalla <[email protected]>
@github-actions
Copy link

Test Results: ❌ FAILED

Run at: 2025-11-27T06:39:18.426Z

Summary:
passed: 910 failed: 7 of 917 tests

@suresh-gangumalla suresh-gangumalla changed the title Addressed issue with computed prop as for loop data Addressed the issue with using a computed prop as the source for loop data. Nov 27, 2025
Signed-off-by: Suresh Kumar Gangumalla <[email protected]>
@github-actions
Copy link

Test Results: ❌ FAILED

Run at: 2025-11-27T07:28:43.714Z

Summary:
passed: 876 failed: 41 of 917 tests

@HadiAlMarzooq
Copy link

Hi @suresh-gangumalla, I've already addressed this in #541, can you check and verify?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants