Import should be handled by one REST API endpoint #190

blcham · 2024-07-21T08:43:27Z

I do not see any advantage of having separate endpoints for JSON and Excel. Assuming there are no technical complications to implement, i suggest joining into one endpoint /import and differentiating which code to execute based on file type.

Originally posted by @blcham in kbss-cvut/record-manager#60 (comment)

…Type} to one single endpoint /rest/records/import

blcham assigned palagdan and unassigned palagdan Jul 21, 2024

blcham transferred this issue from kbss-cvut/record-manager Jul 21, 2024

blcham mentioned this issue Jul 21, 2024

184 support excel import kbss-cvut/record-manager#60

Merged

palagdan mentioned this issue Jul 23, 2024

Import handled by one endpoint 190 kbss-cvut/record-manager#66

Open

palagdan added a commit that referenced this issue Jul 23, 2024

[#190] Change apiUrl in importRecords from /rest/records/import/{file…

964f7a1

…Type} to one single endpoint /rest/records/import

palagdan mentioned this issue Jul 23, 2024

Change apiUrl in importRecords from /rest/records/import/{file… #197

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Import should be handled by one REST API endpoint #190

Import should be handled by one REST API endpoint #190

blcham commented Jul 21, 2024 •

edited

Loading

Import should be handled by one REST API endpoint #190

Import should be handled by one REST API endpoint #190

Comments

blcham commented Jul 21, 2024 • edited Loading

blcham commented Jul 21, 2024 •

edited

Loading