Version

2.x

Issue

There's no handling of multiple declarations of a param on the same property

Suggestion

const p1 = new SpdrSearch('lastname', ['Belmondo']);
const p2 = new SpdrSearch('lastname', ['Delon']);

const qb = new SpdrQueryBuilder([p1,p2]);

Several solutions to this:

• This could throw an exception
• Or glue SpdrParam instances into a single SpdrParam with multiple values when possible. Here it could transform p1 and p2 into const p3 = new SpdrSearch('lastname', ['Belmondo', 'Delon']) , for example.
• Keep only the last instance, that may be the best solution as it would be super handy to use.
• All solutions, depending on an optional parameter, with the exception by default.

Version

3.0.0 and prior

Issue

This would be interesting to split these 3 types of params, as oftentimes you want to update pageIndex, but not the filters, nor the sorting.

Suggestion

const qb = new SpdrQueryBuilder()

qb.params.{whatever filter}()
qb.sort.{whatever sort}()
qb.pagination.{whatever pagination}()

With clearing methods like

qb.sort.clear()

qb.params.search('username', ['johnny'])
qb.params.remove('username')

This way we would be able to update the pagination without the rest and vice versa

{ {...} depends on '@sonicfury/spider-query-builder'. CommonJS or AMD dependencies can cause optimization bailouts.
For more info see: https://angular.io/guide/build#configuring-commonjs-dependencies" }

Probably some configuration issue in tsconfig.json to fix

# ./config/packages/api_platform.yaml
collection:
        pagination:
            page_parameter_name: _page
            items_per_page_parameter_name: itemsPerPage

Add SpiderParams for pagination, with custom param name for both