Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix: GLOBAL_ITERATION_INDEX #726

Merged
merged 2 commits into from
Oct 27, 2023
Merged

Fix: GLOBAL_ITERATION_INDEX #726

merged 2 commits into from
Oct 27, 2023

Conversation

Grafikart
Copy link
Collaborator

Problem

When refactoring the variable system, the GLOBAL_ITERATION_INDEX support was removed.

Solution

When calculating a value in the new system, the variable GLOBAL_ITERATION_INDEX is intercepted and we assign the first iteration level inside (as an integer).
If GLOBAL_ITERATION_INDEX is used in a string it must be cast into a string

Fix #725
Fix #724

@Grafikart Grafikart changed the base branch from main to 2.7 October 18, 2023 16:37
@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

0.0% 0.0% Coverage
0.0% 0.0% Duplication

@romaintailhurat
Copy link
Collaborator

@Grafikart @laurentC35 I dont have any hindsight on the commits themselves but i could validate the behaviour with a dedicated storybook 😅

@laurentC35 laurentC35 merged commit 357c85c into 2.7 Oct 27, 2023
15 checks passed
@laurentC35 laurentC35 deleted the fix/global-iteration-index branch October 27, 2023 08:09
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.

Use of GLOBAL_ITERATION_INDEX to filter a loop GLOBAL_ITERATION_INDEX is a string, should be an integer
3 participants