webiny-admin-architect

Create abstractions with createAbstraction, implement UseCase, Repository, and Gateway classes, then register them via createFeature in admin/features/. The feature must include a resolve function so useFeature can access resolved instances from React.

Use the useFeature hook from webiny/admin, passing the feature definition. It returns whatever the feature's resolve function returned, typically a use case or presenter, which you wrap in a custom hook for typed consumption.

No, never import observer from mobx-react-lite directly. Use createReactiveComponent from webiny/admin in extensions or from @webiny/app-admin in core packages, which is the single source of the re-export.

The most common cause is a missing resolve function in createFeature. Every feature, headless or presentation, must provide resolve so the DI container can return instances to useFeature consumers.

Only as a one-off when the logic is presentation-specific and never reused. The preferred pattern is for presenters to inject a headless feature's use case abstraction as a DI dependency instead of duplicating layering.