-
Notifications
You must be signed in to change notification settings - Fork 2
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
Handle HTTP errors in links #9
Handle HTTP errors in links #9
Conversation
locales/en/messages.json
Outdated
@@ -70,6 +70,7 @@ | |||
"FILE_TYPE_MUST_BE": "Accepted file type:", | |||
"FILE_TYPE_NOT_ACCEPTED": "File type not supported", | |||
"FILES": "Files", | |||
"FILTERS": "Filters", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Intstead of Filters
I would use Show
as a label
options: {}, | ||
}, | ||
}); | ||
indexing.value = false; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
after a reindex we should read the indexed document in order to see if a document has been actually indexed/updated or not
We should call GET /api/brevia/index/{collection_id}/{document_id}
or GET /api/brevia/index/{collection_id}/document_metadata?document_id={document_id}
A user feedback is then needed + change of state (like http_error removal) if something has changed
Aggiunge la gestione degli errori nella parte links del chatbot.
http_error
valorizzato, allora si visualizza con uno sfondo arancione ed il messaggio di errorehttp_error
compare, al posto del pulsante dei metadati, un tasto per reindicizzare ( che richiamaPOST /api/brevia/index/link
)