yes, but it is not the same as in react-admin. You will have to write your custom resource adapter which extends from BaseResource class.

I recently wrote an example app in typescript which shows this approach:

Here is the adapter which wraps JIRA API for projects: https://github.com/wojtek-krysiak/admin-bro-workshop/blob/master/src/jira-projects/jira-project.adapter.ts

and here is how to add this to AdminBroOptions: https://github.com/wojtek-krysiak/admin-bro-workshop/blob/master/src/admin/router.ts#L25

Example uses the latest beta version but it should work with the 1.6.x as well.

Here you can find the documentation for all methods in BaseResource: https://softwarebrothers.github.io/admin-bro-dev/BaseResource.html (1.6v)

or:

https://softwarebrothers.github.io/admin-bro-dev/v2/BaseResource.html (2.0 v)

@wojtek-krysiak Thanks. Is it possible to use AdminBro UI as SPA without any server routing? If so, how could I render root component?

@wojtek-krysiak any help?

you can reuse our design system. It is here: https://github.com/SoftwareBrothers/admin-bro/tree/master/src/frontend/components/design-system. You can copy it to your project and use all the components we build (we have plan to extract this to a separate npm package)

@wojtek-krysiak No, I mean I would like if it would be possible to use auto generated UI for BaseResource as SPA application.
For example in react-admin you need to implement DataProvider and it is possible to create UI for it

render(
    <Admin dataProvider={dataProvider}>
        <Resource name="posts"/>
    </Admin>,
    document.getElementById('root')
);

Is there any plans to support something like this?

no. we dont have this in plans unfortunately :(. but may I ask why you dont want to use react-admin?

It have a pure support for typescript and also it doesn't have something like ResourceOptions so one need to configure everything through components.

What is the advantages of using frontend UI through server instead of SPA approach?

in server version, you have everything out of the box. So, in order to build a working admin panel you just need a database connection - admin generates api routes on the backend with all the CRUD logic. In SPA version you have to maintain backend on our own.

I am leaving this task open and I will add this to a description. Maybe someone will do this.