-
-
Notifications
You must be signed in to change notification settings - Fork 115
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
[2.2.1] Problem after update of document and Tracker recomputation for tags update #228
Comments
Can you please create a small reproduction which could be used as a test case? So something self-contained? |
Sure, I have created a simple reproduction repo, Have tested updates of both firefox 50 and latest chrome in Windows 10 x64 and the error appears consistently. |
That's great progress. Can you make a reproduction without external dependencies? It is hard to make a unit test case with those. |
What kind of dependencies are valid in this case? (I know I have to take out autoForm for example), but are the other packages like validated-method and simple-schema also considered "external dependencies",? (they are pretty common and handy for methods validation at least) |
I mean, yes. Ideally it would be just a snippet of Blaze template which fails. |
(I mean, because I suspect that validated-method and simple-schema are not a reason for this bug. If there is a bug which depends on them, then probably dependency is OK.) |
OK, it seems the issue is |
Yes, in theory label must not appear with label=false. I have updated the repo after removing quite a lot of dependencies (I can continue but probably is something related to autoForm in this case). |
I think I fixed it. Can you try |
Sure give me some minutes and I'll test it against master |
Perfect, just tried it and seems to be fixed! Thanks :) |
Released as 2.3.0. |
Have found this error on the browser console with 2.2.1(not happening with 2.2.0 or previous) where after updating a document (through autoform) multiple errors are printed:
The page gets updated with the new values from the document updated and everything seems to be working, but it sure seems annoying to have all these TypeError: value is null over there.
My autoform is quite simple so I'm guessing the error will also happen with normal forms. It looks quite like this:
The text was updated successfully, but these errors were encountered: