You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There doesn't seem to be any reason for url to be invalidated here, and it causes an infinite loop. Using $: fetch(url).then(r => { resp = r; }); instead invalidates only resp as expected.
The text was updated successfully, but these errors were encountered:
I think this is the result of the change in #2694. The return that happens here only when we pass a value is confusing me. I don't know why that's the only case we want to skip the recursive invalidation. I'm not actually sure what it means to pass or not pass that second argument to invalidate. If we here instead call it with component.invalidate(name, name), that seems to address this particular issue, but I have no idea what the other implications of this are. It doesn't appear to break any existing tests. Nor does doing that a few lines lower in the /Statement/ branch.
With something like this, the compiler produces
There doesn't seem to be any reason for
url
to be invalidated here, and it causes an infinite loop. Using$: fetch(url).then(r => { resp = r; });
instead invalidates onlyresp
as expected.The text was updated successfully, but these errors were encountered: