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
I have seen another underscore issue with _.intersection, but it seems to be a different problem.
If you need any more information, i will be happy to help ;)
The text was updated successfully, but these errors were encountered:
Yes, I know aldeed/autoform@6.3.0 is outdated 😅 and we're working on updating it now, but it sounds like there are other affected dependants :).
Would it be possible to revert the _.where change? We could help with a PR if you like.
Just in case anyone needs a short-term workaround - Meteor allows for override packages, even core, by placing the package source code in the packages folder in your application's root.
Hi,
I'm using and reproducing this with meteor on Mac (version 14.2.1) and ubuntu (version 20.04.6)
Since Meteor 2.15, with the upgrade of underscore from 1.0.13 to 1.6.1 .
The return of the function _.where(array, {criteriaToFind}) seems to always be the first element to correspond to the search.
In previous meteor versions, the function _.where used to return an array of every items find.
I made a repository to reproduce the problem.
https://github.com/LionelGuerin/meteor_underscore_where
It's composed of three folders to tests with meteor 2.15 , meteor 2.14 and with vanilla underscore NPM.
For meteor 2.15
Go to your browser then click on "Click Me"
You should see the following server log
For meteor 2.14
Go to your browser then click on "Click Me"
You should see the following server log
For vanilla underscore NPM
You should see the following log
I have seen another underscore issue with _.intersection, but it seems to be a different problem.
If you need any more information, i will be happy to help ;)
The text was updated successfully, but these errors were encountered: