With the new applications filtering, the existing application/listing fetch performance is being exacerbated by re-fetching the data each time the user selects a different type of application to view. For example, 10 applications would result in 11 calls to the BE (1 to list applications and 10 to fetch each associated listing). Additionally, a ton of additional data is being sent that isn't necessary and it requires significant FE business logic to map the results to the user's experience.
This ticket is intended to simplify this process to a single call and minimize the FE business logic so that user's have a more performant experience and they're significantly less likely to encounter throttling in their use of this feature.
QA (Handled by Eng @ColinBuyck )
This can be tested by signing into an account, applying to more than one listing, and seeing in the network tab that only one call is being made no matter how many listings there are.
With the new applications filtering, the existing application/listing fetch performance is being exacerbated by re-fetching the data each time the user selects a different type of application to view. For example, 10 applications would result in 11 calls to the BE (1 to list applications and 10 to fetch each associated listing). Additionally, a ton of additional data is being sent that isn't necessary and it requires significant FE business logic to map the results to the user's experience.
This ticket is intended to simplify this process to a single call and minimize the FE business logic so that user's have a more performant experience and they're significantly less likely to encounter throttling in their use of this feature.
QA (Handled by Eng @ColinBuyck ) This can be tested by signing into an account, applying to more than one listing, and seeing in the network tab that only one call is being made no matter how many listings there are.