Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

'parsed' field blowing up the database #85

Open
felipefreitag opened this issue Feb 9, 2022 · 2 comments
Open

'parsed' field blowing up the database #85

felipefreitag opened this issue Feb 9, 2022 · 2 comments
Assignees
@felipefreitag

Comments

@felipefreitag
Copy link
Contributor

The 'parsed' field can't be sent to the DB because it can contain MB of data and crash the application.
@felipefreitag
Copy link
Contributor Author

Proposal: start by removing the parsed field from this internal type
Something like
export type FileState = { [key: string]: Omit<FileData, 'parsed'> }
Leave it on FileData for the API interface, but remove it from Uploods internal state.

@felipefreitag
Copy link
Contributor Author

Maybe filter the field here

@gustavoguichard gustavoguichard removed their assignment Oct 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@felipefreitag felipefreitag

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gustavoguichard @felipefreitag