2022-12-13 17:09:57 |
Tiffany Little |
description |
Spun off from bug 1999544.
Basically, you can type ahead in the fund dropdowns and find funds that aren't automatically populating. They then appear in your dropdown list. However, if you leave that modal and return, they're no longer in the dropdown list. So the usefulness of having them appear in the list is pretty much nil.
It seems like this might stem from fetchFunds in acq/lineitem/lineitem.service.ts? I think we're caching the funds, but they're not sticking in the cache for some reason?
The issue is that even once bug 1999544 is fixed, we do have libraries with more than 100 active funds. If fetchFunds is intended to work like: "fund is past the 100 limit, typeahead to search, now populated in list (in cache), now will show up subsequent fund dropdowns."
If that's the intended purpose, then we do need that for those 100+ fund libraries so they can actually see a list of their available funds. |
Spun off from bug 1999544.
Basically, you can type ahead in the fund dropdowns and find funds that aren't automatically populating. They then appear in your dropdown list. However, if you leave that modal and return, they're no longer in the dropdown list. So the usefulness of having them appear in the list is pretty much nil.
It seems like this might stem from fetchFunds in acq/lineitem/lineitem.service.ts? I think we're caching the funds, but they're not sticking in the cache for some reason?
The issue is that even once bug 1999544 is fixed, we do have libraries with more than 100 active funds. If fetchFunds is intended to work like: "fund is past the 100 limit, typeahead to search, now populated in list (in cache), now will show up subsequent fund dropdowns."
If that's the intended purpose, then we do need that for those 100+ fund libraries so they can actually see a list of their available funds without typing ahead every single time. |
|