eeb04ae436
* Add Partition to all our models * Add partitions into our serializers/fingerprinting * Make some amends to a few adapters ready for partitions * Amend blueprints to avoid linting error * Update all our repositories to include partitions, also Remove enabled/disable nspace repo and just use a nspace with conditionals * Ensure nspace and parition parameters always return '' no matter what * Ensure data-sink finds the model properly This will later be replaced by a @dataSink decorator but we are find kicking that can down the road a little more * Add all the new partition data layer * Add a way to set the title of the page from inside the route and make it accessibile via a route announcer * Make the Consul Route the default/basic one * Tweak nspace and partition abilities not to check the length * Thread partition through all the components that need it * Some ACL tweaks * Move the entire app to use partitions * Delete all the tests we no longer need * Update some Unit tests to use partition * Fix up KV title tests * Fix up a few more acceptance tests * Fixup and temporarily ignore some acceptance tests * Stop using ember-cli-page-objects fillable as it doesn't seem to work * Fix lint error * Remove old ACL related test * Add a tick after filling out forms * Fix token warning modal * Found some more places where we need a partition var * Fixup some more acceptance tests * Tokens still needs a repo service for CRUD * Remove acceptance tests we no longer need * Fixup and "FIXME ignore" a few tests * Remove an s * Disable blocking queries for KV to revert to previous release for now * Fixup adapter tests to follow async/function resolving interface * Fixup all the serializer integration tests * Fixup service/repo integration tests * Fixup deleting acceptance test * Fixup some ent tests * Make sure nspaces passes the dc through for when thats important * ...aaaand acceptance nspaces with the extra dc param |
||
---|---|---|
.. | ||
index.hbs | ||
index.js | ||
README.mdx |
# DataCollection The DataCollection component is the component we use for searching, filtering and sorting. It does not dictate any rendering of your data, but it does provide two different states/contextual components for rendering: when there are some results, when there are no results and also (by not using the contextual components) when the amount of results does not matter to what you want to render (say a count of number of results). The component should be configured with the `@type` attribute, the component will use this to lookup 'specifications' for searching, sorting and filtering in the respective `app/search/predicates`, `app/sort/comparators` and `app/filter/predicates` folders. These specifications define _what_ is searched when you search a list of objects (for example searching Name could mean searching `model.Name` whereas searching Role could mean searching through an array of `item.RoleDefaults`). The component can also be further configured by specifications for _how_ to search, for example we currently only use `Exact` searching (pretty much an `indexOf` search), but we also have `fuzzy` and `regexp` searching methods available (but disabled until needed). These search 'methods' will use the above specifications again to define _what_ to search. Searching methods (the _how_) are in `utils/search/{exact,fuzzy,regexp}.js` and any new ones should implement at least a single `search` method. Lastly, a `SearchService` in `services/search.js` configures what is available for _what_ to search and _how_ to search, so if you need to add new models or search methods, that is where to look. ```hbs preview-template <figure> <figcaption>Provide a widget to search with</figcaption> <input oninput={{action (mut this.term) value="target.value"}} type="text" /> </figure> <figure> <figcaption>Get some data to search on</figcaption> <DataSource @src="/partition/nspace/dc-1/services" as |source|> <figure> <figcaption>and show the complete set of data</figcaption> {{#each source.data as |item|}} {{item.Name}}, {{/each}} </figure> <hr /> <figure> <figcaption>Use the component</figcaption> <DataCollection @type="service" @search={{this.term}} @sort={{'Name:asc'}} @filter={{hash searchproperties=(array 'Name') }} @items={{source.data}} as |collection|> Has {{collection.items.length}} results:<br /> <collection.Collection> {{#each collection.items as |item|}} {{item.Name}}, {{/each}} </collection.Collection> <collection.Empty> Is Empty </collection.Empty> </DataCollection> </figure> </DataSource> </figure> ``` ### Arguments | Argument | Type | Default | Description | | --- | --- | --- | --- | | `items` | `Array` | [] | The collection of data to search/sort/filter | | `search` | `String` | '' | A search term to use for searching | | `sort` | `String` | '' | A sort term to use for sorting on ('Name:asc') | | `filter` | `Object` | | An object whose properties are the properties/values to filter on | | `type` | `String` | '' | The name of the specification describing what to search, filter, sort | | `searchable` | `String` | `exact` | The name of the method to use for searching | ### Yields The DataCollection yields an object containing the following: | Property | Type | Description | | --- | --- | --- | | `items` | `Array` | The resulting collection of data after searching/sorting/filtering | | `search` | `Function` | An action used to perform a search - takes a single string argument that should be the search term | | `Collection` | `Component` | A slot-like component that only renders when the items in the collection is greater than 0 | | `Empty` | `Component` | A slot-like component that only renders when the items in the collection is 0 | ### See - [Component Source Code](./index.js) - [Template Source Code](./index.hbs) ---