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.

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

Corpus Import Needs More Guardrails #77

Closed
JSv4 opened this issue Feb 20, 2023 · 1 comment
Closed

Corpus Import Needs More Guardrails #77

JSv4 opened this issue Feb 20, 2023 · 1 comment

Comments

@JSv4
Copy link
Owner

JSv4 commented Feb 20, 2023

Accidentally imported a .pdf as a corpus instead of a document. This created a placeholder corpus and kicked off importer. The importer rightly detected the incorrect file type and threw and error, but a) I didn't get this error on the frontend and b) I know have a corpus I didn't expect.

Suggest the exports are given a custom extension and import is restricted to files with those extensions on the frontend.

@JSv4
Copy link
Owner Author

JSv4 commented Jul 9, 2024

Suggest this be rolled into #140

@JSv4 JSv4 closed this as completed Jul 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant