Ashot Nazaryan
Ashot Nazaryan
https://gist.github.com/AshotN/bdcf8fa86e66366cb0ad
I tried to figure it out, but i couldn't :( But I'll try again
Is there any plans to implement this? The component that was shared in the original issue is out of date
I also believe https://github.com/SoftwareBrothers/adminjs/blob/9bb269cab385376525728699f8201cebf0e47bd0/src/adminjs-options.interface.ts#L101 falls into this issue The usage of `| any` boils the type down to `Array`
I was able to resolve this by doing this ``` const DASHBOARD = AdminJS.bundle("./components/Dashboard") ... new AdminJS({ rootPath: "/", logoutPath: "/logout", assetsCDN, dashboard: { component: DASHBOARD, }, resources: [ ......
I believe I tried that, and it still caused a mis match of components. Instead of Component1 it became dashboard. But there was no Component1, started from Component2. I can...
My train of thought is a bit lost by now, but I can reproduce this issue still when building for production. This is my start/build script. ``` "start:local:deployTest": "yarn build...
This seems to effect custom pages in general.
Throwing a regular Error won't work, because `baseMessage` is not a property in a normal `Error` object AdminJS has `ForbiddenError` that has a `baseMessage` property. It works if I throw...
Can we compromise with a new error type that isn't `ForbiddenError` just for semantics