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

The palette condition for visible property, produce a maximum nested error. #528

Open
baumannsven opened this issue Apr 24, 2020 · 1 comment
Assignees
Milestone

Comments

@baumannsven
Copy link
Member

There are many view conditions for visible properties. So there is the danger of triggering the error.

To solve this problem you should use an array cache which contains the evaluated properties and legends.

These conditions are affected:

For these conditions the array cache is added using constructor. This is added as an optional parameter for the time being. Later in version 3.0 the optional one will be removed and must be set. This is also known as a deprecated notice. So you can use this condition without any changes and use the new feature immediately.

@baumannsven baumannsven added this to the 2.2.0 milestone Apr 24, 2020
@baumannsven baumannsven self-assigned this Apr 24, 2020
@discordier
Copy link
Member

After discussion on mumble, @baumannsven will provide a valid test case in the test website to reproduce the original issue.

@zonky2 zonky2 modified the milestones: 2.2.0, 2.3.0 May 10, 2022
@zonky2 zonky2 modified the milestones: 2.3.0, 2.3.1 Oct 31, 2023
@zonky2 zonky2 modified the milestones: 2.3.1, 2.2.3, 2.4.0 Nov 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants