How vineets46/invoiceflow works
Project type and purpose
• This is a full-stack invoice management web application (“InvoiceFlow”).
• Frontend: React SPA (bootstrapped with Create React App) under the root src and public folders.
• Backend: Serverless functions in invoiceflow-backend (Azure Functions).
• Auth & Persistence: Firebase for user authentication and Firestore for storing invoice metadata (in src/firebaseConfig.js).
• File processing: Users upload invoice PDFs via a presigned-URL flow; a storage trigger processes them.
File structure
• Root:
• public & src → React app sources, assets, components, hooks, pages.
• firebaseConfig.js & useAuth.js → Firebase Auth / Firestore integration.
• invoiceflow-backend → Azure Functions project:
– getUploadUrl (HTTP-trigger)
– processInvoice (Blob-trigger)
– host.json, .funcignore → function runtime configuration
• Patterns:
• SPA with protected routes (ProtectedRoute.js)
• Serverless microservices (two functions)
• Event-driven processing (blob trigger)
README
• Standard CRA instructions—no bespoke architecture doc.
Final advice
• Be very detailed—break out each function and each SDK interaction.
• Don’t overthink—separate the system into its logical components (Auth, API, Storage, Processing, DB, UI).
• Both synchronous (HTTP) and asynchronous (event) flows.