mirror of
https://github.com/ascribe/onion.git
synced 2024-11-15 01:25:17 +01:00
d23331d9b9
ReactS3FineUploader used to check the current url’s query params to determine which method it should use to upload, but this decision means the component is tightly coupled with react-router and history.js. A major pain point is having to propagate the location prop all the way down to this component even when it’s not necessary. Now, ReactS3FineUploader’s parent elements can either parse the current query params themselves or, if they have a location from react-router, simply use the location. Added a few utils to help parse url params.
41 lines
1.1 KiB
JavaScript
41 lines
1.1 KiB
JavaScript
'use strict';
|
|
|
|
import requests from '../utils/requests';
|
|
|
|
import { mergeOptions } from '../utils/general_utils';
|
|
import { generateOrderingQueryParams } from '../utils/url_utils';
|
|
|
|
let PieceListFetcher = {
|
|
/**
|
|
* Fetches a list of pieces from the API.
|
|
* Can be called with all supplied queryparams the API.
|
|
*/
|
|
fetch(page, pageSize, search, orderBy, orderAsc, filterBy) {
|
|
let ordering = generateOrderingQueryParams(orderBy, orderAsc);
|
|
|
|
// filterBy is an object of acl key-value pairs.
|
|
// The values are booleans
|
|
let queryParams = mergeOptions(
|
|
{
|
|
page,
|
|
pageSize,
|
|
search,
|
|
ordering
|
|
},
|
|
filterBy
|
|
);
|
|
|
|
return requests.get('pieces_list', queryParams);
|
|
},
|
|
|
|
fetchRequestActions() {
|
|
return requests.get('pieces_list_request_actions');
|
|
},
|
|
|
|
fetchFirstEditionForPiece(pieceId) {
|
|
return requests.get('piece_first_edition_id', {'piece_id': pieceId});
|
|
}
|
|
};
|
|
|
|
export default PieceListFetcher;
|