You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While creating custom entities in Vendure is a streamlined process with a great developer experience, displaying and managing these entities in the Admin UI currently requires manual work. Developers need to create custom Angular components for both list and detail views, along with custom forms to manage the data.
Although this provides flexibility for tailoring the Admin UI to specific business workflows, it can be overly complex when the goal is simply to enable admin users to create, update, or read custom entities.
The config-based list and detail views will leverage Vendure's Typescript-based configuration system, similar to the one used for custom fields. This will allow developers to define custom UI extensions for custom entities without needing to write Angular code. The system will automatically generate list and detail views in the Admin UI, significantly improving the developer experience and speeding up the development process.
Motivation
Simplify the process of exposing custom entities in the Admin UI by reducing the need for custom Angular components and forms.
Enable rapid development by automating the generation of list and detail views through a configuration-based approach.
Maintain flexibility for more complex cases while offering a streamlined path for simpler use cases where custom entities need to be managed in the Admin UI.
Proposed Solution
Implement a configuration-based system, similar to custom fields, that allows developers to define list and detail views for custom entities through TypeScript-based config files.
Automatically generate the necessary UI components for list and detail views in the Admin UI without the need for manual Angular coding.
Ensure that this approach integrates smoothly with existing custom fields and Admin UI extensions, enabling developers to mix custom code with configuration-based setups as needed.
Additional Context
The goal is to enhance the developer experience and accelerate development workflows by reducing the overhead involved in exposing custom entities in the Admin UI. This will help developers build faster without sacrificing the ability to customize workflows where needed.
Description
Motivation
Proposed Solution
Additional Context
The goal is to enhance the developer experience and accelerate development workflows by reducing the overhead involved in exposing custom entities in the Admin UI. This will help developers build faster without sacrificing the ability to customize workflows where needed.
This will be done together with #2903
The text was updated successfully, but these errors were encountered: