title | layout | nav_order |
---|---|---|
Api |
post |
3 |
The api
define a fetch
function which is there to hide the WordPress Fetch API. The reason behind this decision lies on the fact that we might want to add middlewares to the request in the future or introducing some global data manipulation.
The package provide then the following functions to interact with the WordPress API:
This function is a wrapper for the Search Endpoint of the WordPress API. It will return a Set
of entities matching the search query.
The possible query arguments are specified by the Kensaku.QueryArguments
type, an interface you can expand to add more arguments.
This function is not directly consumed by the components, and it is not intended to be used internally. The idea is to follow the Tell don't Ask principle and let the consumer specify how to search the Entities.
Below a possible example of its usage related to a component:
// my-component.tsx
type Search = Kensaku.SearchEntitiesFunction<string, string>;
type Props = {
search: Search
}
const MyComponent (props: Props) => {
const [entities, setEntities] = useState<Set>(new Set());
useEffect(() => {
props
.search(
'my search phrase',
'post',
new Set(['page']),
{
per_page: 10,
fields: ['slug', 'title']
}
)
.then(setEntities);
}, []);
// Do something with the entities
}
// index.tsx
import {searchEntities} from 'kensaku';
root.render(<MyComponent search={searchEntities} />);
The function accept four parameters
type
- The root type. We have two built-int supported typespost
,term
.subtype
- The subtype of the entity. For example, if thetype
ispost
, thesubtype
can bepage
,post
, etc. WordPress exclude automatically theattachment
subtype.phrase
- The search phrase. This becomes thes
parameter for the Search Endpoint.queryArguments
- All the supported and extra query arguments. TheKensaku.QueryArguments
type is an interface you can expand to add more arguments.
The function return an immutable Set
of entities.
NOTE: The function does not handle possible request exceptions.
The searchEntities
will automatically abort the requests with the same parameters if a new request is made before the previous one is completed.
This function is a wrapper for the searchEntites
which perform a small additional task you might want to do quite ofter after retrieving the entities that is
to convert the entities to Kensaku.ControlOptions
. The argument taken are the same of the searchEntities
.
This is a factory function, it returns a searchEntitiesOptions
function preconfigured to search for a specific root kind.
For instance, if we call this function with post
like createSearchEntitiesOptions('post')
the returned function will be of type searchEntitiesOptions
where you don't always have to pass the root type.
Most probably this will be the function you'll deal with most as it make easy to build a function you can consume with other components.