We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently, invalidating fields if one of their dependencies changed does not cascade. This means that given I have the following fields
A --> B --> C Depends on A Depends on B
if A gets changed, B should be invalidated. Since B has now been changed as well, C should also be invalidated.
A
B
C
This is currently not the case. Right now, only B would get invalidated and it would not cascade further.
The text was updated successfully, but these errors were encountered:
I'll take a look into this
Sorry, something went wrong.
ksassnowski
No branches or pull requests
Currently, invalidating fields if one of their dependencies changed does not cascade. This means that given I have the following fields
if
A
gets changed,B
should be invalidated. SinceB
has now been changed as well,C
should also be invalidated.This is currently not the case. Right now, only
B
would get invalidated and it would not cascade further.The text was updated successfully, but these errors were encountered: