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
For the new PSLF and C4C collections, when filter is set, displays no projects, but loads in the correct number of projects that are supposed to be there. Other collections work as intended.
The text was updated successfully, but these errors were encountered:
I've notice it too 5 min ago and I've just pushed a fix.
The list of collection that appear in the filter for the project collection is hardcoded.
But the problem was that because we order by budget*readability it was expecting a budget but there is no budget on those projects so i've put the budget as OPTIONAL and now it should be working
And btw does this filter should go to the index release ? If yes it mean that we are going to need to make an updtae of the backend too to add this project collection and the fix for the OPTIONAL budget (in total it's something like 5 line of code that changed for that)
Thanks @DiaZork for addressing! And yes, these two collections are basically the reason why we are doing the index release in the first place, so if you could add that to the backend, would be great!
Also, @DiaZork, do not forget to make it filterable on the map. I just checked on the one on dev, and it just spins forever if you filter for those specific collections, just make sure it works with the map version we aim to do the index update with
For the new PSLF and C4C collections, when filter is set, displays no projects, but loads in the correct number of projects that are supposed to be there. Other collections work as intended.
The text was updated successfully, but these errors were encountered: