* fix after rebase * new release strategy for ng next Signed-off-by: eromano <eugenioromano16@gmail.com> * peer dep Signed-off-by: eromano <eugenioromano16@gmail.com> * Angular 14 fix unit test and storybook Signed-off-by: eromano <eugenioromano16@gmail.com> fix after rebase Signed-off-by: eromano <eugenioromano16@gmail.com> update pkg.json Signed-off-by: eromano <eugenioromano16@gmail.com> missing dep Signed-off-by: eromano <eugenioromano16@gmail.com> Fix mistake and missing code Dream....build only affected libs Add utility run commands * Use nx command to run affected tests * Fix nx test core fix content tests Run unit with watch false core test fixes reduce test warnings Fix process cloud unit Fix adf unit test Fix lint process cloud Disable lint next line Use right core path Fix insights unit fix linting insights Fix process-services unit fix the extensions test report fix test warnings Fix content unit Fix bunch of content unit * Produce an adf alpha of 14 * hopefully fixing the content * Push back the npm publish * Remove flaky unit * Fix linting * Make the branch as root * Get rid of angualar13 * Remove the travis depth * Fixing version for npm * Enabling cache for unit and build * Fix scss for core and paths Copy i18 and asset by using ng-packager Export the theming alias and fix path Use ng-package to copy assets process-services-cloud Use ng-package to copy assets process-services Use ng-package to copy assets content-services Use ng-package to copy assets insights * feat: fix api secondary entry point * fix storybook rebase * Move dist under dist/libs from lib/dist * Fix the webstyle * Use only necessary nrwl deps and improve lint * Fix unit for libs * Convert lint.sh to targets - improve performance * Use latest of angular * Align alfresco-js-api Signed-off-by: eromano <eugenioromano16@gmail.com> Co-authored-by: eromano <eugenioromano16@gmail.com> Co-authored-by: Mikolaj Serwicki <mikolaj.serwicki@hyland.com> Co-authored-by: Tomasz <tomasz.gnyp@hyland.com>
3.7 KiB
Title, Added, Status
Title | Added | Status |
---|---|---|
Search Configuration interface | v2.1.0 | Active |
Search Configuration interface
Provides fine control of parameters to a search.
Methods
generateQueryBody(searchTerm: string, maxResults: string, skipCount: string): QueryBody
Generates a QueryBody object with custom search parameters.
Details
The interface defines a service that generates a custom QueryBody object. This object can then be supplied to a search operation to refine the search parameters.
A standard implementation, the Search Configuration service is provided in the ADF Core library source. This works fine in most cases but if you need to, you can implement your own service, as described below.
How to use the interface
-
Implement the service class
Create your own service class to implement the
SearchConfigurationInterface
. This defines the thegenerateQueryBody
method that returns the QueryBody object. See the QueryBody page in the Alfresco JS API for further details about the options this object provides.An example implementation is given below:
import { QueryBody } from '@alfresco/js-api'; import { SearchConfigurationInterface } from '@alfresco/adf-core'; export class TestSearchConfigurationService implements SearchConfigurationInterface { constructor() { } public generateQueryBody(searchTerm: string, maxResults: string, skipCount: string): QueryBody { const defaultQueryBody: QueryBody = { query: { query: searchTerm ? `${searchTerm}* OR name:${searchTerm}*` : searchTerm }, include: ['path', 'allowableOperations'], paging: { maxItems: maxResults, skipCount: skipCount }, filterQueries: [ { query: "TYPE:'cm:folder'" }, { query: 'NOT cm:creator:System' }] }; return defaultQueryBody; } }
-
Provide your service class to the module
Once you have created your service class, you must inform the component to use it instead of the default one. This is easily done using the component providers:
import { SearchService, SearchConfigurationService } from '@alfresco/adf-core'; import { TestSearchConfigurationService } from './search-config-test.service'; @Component({ selector: 'app-search-extended-component', templateUrl: './search-extended.component.html', styleUrls: ['./search-extended.component.scss'], encapsulation: ViewEncapsulation.None, providers: [ { provide: SearchConfigurationService, useClass: TestSearchConfigurationService }, SearchService ] })
You also need to add the
SearchService
as a provider to avoid overriding the module instance. This component will have his own instance of theSearchService
that will use the class you have provided as its configuration.