Addresses are missing on projects/show

[hannahkates]

There is a limit to the total number of expansions you can do (5).

[allthesignals]

I was thinking, i could grab these through the BBLs asynchronously. we at least have the bbls. I could query carto pluto for those.

[allthesignals]

we could also just grab this data direct from crm api asynchronously. the only reason they aren't showing up is i can only inner join 5 entities in a single request. a subsequent req wwould work:

/projects/:id/addresses

[hannahkates]

@allthesignals Async is probably best. I think we have the use the official, preferred addresses stored in ZAP CRM. They can be different than the ones provided per BBL in MapPLUTO and there isn't always a 1-1 relationship between BBLs on a project and addresses on a project.

[allthesignals]

makes sense. easy to do an async endpoint for those.

[allthesignals]

Create a projects/:id/addresses endpoint in backend, and have frontend request this resource

[trbmcginnis]

@allthesignals Should the buildout of this new endpoint wait until we update labs-zap-api to connect directly to CRM? So that I'm not building out this endpoint using the old method

[hannahkates]

@trbmcginnis This problem isn't on production with the existing live API. It's caused by the new Web API implementation, so the fix would be within the same branch as the new Web API implementation.