Skip to content

WIP Unnest search param#81

Draft
ttill wants to merge 8 commits intonickschot:masterfrom
ttill:unnest-search-param
Draft

WIP Unnest search param#81
ttill wants to merge 8 commits intonickschot:masterfrom
ttill:unnest-search-param

Conversation

@ttill
Copy link
Copy Markdown
Contributor

@ttill ttill commented May 8, 2020

Adds nestSearchParam argument, to be able to support backends which require search params without any nesting, such as &search=<TERM>. The current behaviour (&searchProperty[searchKey]=<TERM>) remains the default choice.

Fixes #80.

This is based on #78 and will be rebased on master once the former is merged.

ttill added 8 commits April 8, 2020 13:00
* Also fixes usage of onInput

TODO
* Update ember-try config (ember-power-select only works on Ember 3.11+)
* Fix tests failures related to ember-infinity
* Refactor to glimmer components
* Min Ember.js version is 3.13 instead of 3.12 because tracked
  properties are used
Also fix/update docs on global configuration.
@nickschot
Copy link
Copy Markdown
Owner

I'm thinking as we're doing a major release anyway if maybe we should change the behaviour to allow omitting the searchProperty (and then it'd only use the searchKey)? Might make more sense instead of introducing more options.

@ttill
Copy link
Copy Markdown
Contributor Author

ttill commented Jul 4, 2020

Sure, sounds like a cleaner approach.

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

Successfully merging this pull request may close these issues.

Make it possible to have an empty searchKey

2 participants