Getting stuck on the implementation

[ReisoAphi]

Im Getting this msg from the adminJs app: "You have to implement action component for your ActionSee:the documentation"

Any clue?

[joncottrell]

Same issue here. @ReisoAphi what did you end up doing?

[Brdnn]

I am facing the same issue, any workaround there?

[ZeroCho]

    componentLoader,
    resources: [createUserResource(componentLoader)],

I think you guys didn't put componentLoader option above resources option

[vikas21222]

Im Getting this msg from the adminJs app: "You have to implement action component for your ActionSee:the documentation"

also facing the same issue

[ahmetson]

It happens because the ComponentLoader passed to the ImportExport feature is not known by Adminjs.
You should pass the component loader that's used by Adminjs to the ImportExportFeature.

Correct format of the app.js is:

import { ComponentLoader } from 'adminjs'

const componentLoader = new ComponentLoader()

 const adminOptions: AdminJSOptions = {
    componentLoader,
    resources: [createCustomResource(componentLoader)]
    }
 }

const adminjs = new AdminJS(adminOptions);

Now, the script that defines the resource with the ImportExportFeature:

let createCustomResource = (componentLoader) => {
   return {
      resource: DatabaseModel,
      features: [
            importExportFeature({ componentLoader }),
       ],
   }
}

If you define the componentLoader in the script with the resource using new ComponentLoader() and it's not passed to the adminjs, then you will see the error.

In short, you should have only one instane of ComponentLoader within your app.

[lpbonomi]

@ahmetson looks like this works, maybe this should go in the docs?

[vikas21222]

It happens because the ComponentLoader passed to the ImportExport feature is not known by Adminjs. You should pass the component loader that's used by Adminjs to the ImportExportFeature.

Correct format of the app.js is:

import { ComponentLoader } from 'adminjs'

const componentLoader = new ComponentLoader()

 const adminOptions: AdminJSOptions = {
    componentLoader,
    resources: [createCustomResource(componentLoader)]
    }
 }

const adminjs = new AdminJS(adminOptions);

Now, the script that defines the resource with the ImportExportFeature:

let createCustomResource = (componentLoader) => {
   return {
      resource: DatabaseModel,
      features: [
            importExportFeature({ componentLoader }),
       ],
   }
}

If you define the componentLoader in the script with the resource using new ComponentLoader() and it's not passed to the adminjs, then you will see the error.

In short, you should have only one instane of ComponentLoader within your app.

not usefull for me still getting same error

[lpbonomi]

In my case, I wasn't bundling the components after using admin.watch() and admin.initialize() it worked

[juanjofrelopez]

@ReisoAphi Hi! Any solution to this? I'm facing the same problem with the export functionality. Thanks

[ReisoAphi]

Whenever you add a React implementation, you need to bunddle. Add to your admin app a watcher, admin.watch(), let the app run and it will bundle whenever the app sees a react change.

And dont forget to add the feature to your table features property.

[vovantics]

I too got this "You have to implement action component for your ActionSee:the documentation" error.

I also observed the following stdout when starting my Admin.js app:

admin-1  | AdminJS available at http://0.0.0.0:3000/
admin-1  | "date-fns/format" is imported by "../../node_modules/@adminjs/import-export/lib/components/ExportComponent.jsx", but could not be resolved – treating it as an external dependency.
admin-1  | - Bundling files...
admin-1  | "date-fns/format" is imported by "../../node_modules/@adminjs/import-export/lib/components/ExportComponent.jsx", but could not be resolved – treating it as an external dependency.
admin-1  | No name was provided for external module "date-fns/format" in "output.globals" – guessing "format".
admin-1  | ✔ Finish bundling: 27 files

The problem is that 'date-fns/format' is imported in ExportComponent.tsx but defined as a dev dependency in @adminjs/import-export.

I worked around it by adding "date-fns": "^4.1.0" as a dependency in my Admin.js app.

I think the correct solution is to define "date-fns/format" as a dependency instead of a dev dependency.