0.1.0 • Published 9 months ago

@kit-data-manager/react-fairdo-search v0.1.0

Weekly downloads
-
License
Apache-2.0
Repository
github
Last release
9 months ago

fairdo-elastic-search

Static Badge Node.js CI NPM Type Definitions

All-in-one, highly configurable React component for rendering an elastic search UI based on the provided configuration. Includes an interactive graph of related records.

This is an ESM Module intended for use in modern React applications. Make sure your bundler supports importing CSS files in JavaScript/TypeScript. Next.js is supported out of the box.

Installation

  npm install @kit-data-manager/react-fairdo-search

Docs

Visit the Storybook for examples and some documentation. For more documentation, consult the TypeScript typings.

Quick Start

Refer to the Getting Started Guide in the Storybook

Customization

Result View

Most notably, the result view component should be customized. A GenericResultView Component is provided that should work for some scenarious out of the box. Otherwise, you should implement your own Result View in React. For a starting point, feel free to copy the code of GenericResultView.ts, though most of the customization should be thrown out to make it more lightweight.

Generic Result View

Each field of the generic result view can be mapped to a field in the elastic search index. Additionally, you can specify multiple tags from multiple different fields in the elastic index. Take a look at the Storybook for an example.

To map (parts of) the result before feeding it to the GenericResultView, you can define you own component that itself uses the GenericResultView with modified data:

import { useMemo } from "react"
import { GenericResultView, ResultViewProps } from "@kit-data-manager/react-fairdo-search"

export function MyResultView(props: ResultViewProps) {
    const mappedResult = useMemo(() => {
        const copy = structuredClone(props.result)
        copy.someProperty = copy.something + copy.somethingElse
        return copy
    }, [props.result])

    return <GenericResultView result={mappedResult} titleField={"someProperty"} />
}

Then simply pass your custom component to the search component.

Styling

Styling is done using tailwind and css variables. Feel free to override these variables in your own CSS.

Contributing

Feedback and issue reports are welcome, simply create an issue here on GitHub.

Development

Install dependencies with

    npm install

Run development server with

    npm run storybook:dev