Closed allthesignals closed 1 year ago
This is built in what looks like a dead framework: https://www.npmjs.com/package/fortune-http.
Getting a few errors with certain deps... blew out node_modules and yarn.lock for a fresh rebuild, seeing success!
No test suite unfortunately so can't quite tell what's going on with it.
Whoa! I'm in the frontend repo. Not the backend. We should merge the two!
I see, this repo doesn't have issues enabled: https://github.com/NYCPlanning/labs-applicantmaps-api. Let me make a personal fork. note: @TylerMatteo, need permissions to access this.
PR for the backend code: https://github.com/NYCPlanning/labs-applicantmaps-api/pull/13
@TylerMatteo https://applicantmaps-staging.planninglabs.nyc/projects/new
EDIT: was this staging env ever working?
{"data":{"attributes":{"annotations":{"type":"FeatureCollection","features":[{"type":"Feature","geometry":null,"properties":{"isEmptyDefault":true}}]},"project-name":"My awesome project","applicant-name":null,"zap-project-id":null,"description":null,"date-prepared":0,"step-label":null,"need-development-site":null,"need-project-area":null,"need-rezoning":null,"need-underlying-zoning":null,"need-commercial-overlay":null,"need-special-district":null,"has-completed-wizard":null},"type":"projects"}}
@allthesignals Deployed this to production today. I'm pretty sure that error you were seeing in staging was because it's db connection string was a dead link. Closing
This issue is closed when the app builds for Node 14/16