fix: Handle read-only filesystem on Vercel for logger #196
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR includes two main improvements:
1. Database Schema Refactoring
userfield touserId(String) in InterviewQuestion, LeetcodeQuestion, and Tips modelscompanyNamefield to Application and SavedApplication models for denormalization.populate()calls for userId (no longer an ObjectId)Breaking Changes:
userIdinstead ofusercompanyNamefield2. Vercel Logger Fix
EROFS: read-only file systemerror on Vercel deploymentsChanges Made
Briefly summarize the major changes:
user→userIdin InterviewQuestion, LeetcodeQuestion, Tips modelscompanyNamefield to Application and SavedApplication models.populate({ path: "user" })calls from controllersuserIdand validatecompanyNameTesting
Testing details: