widget-development

To scaffold a React widget, copy the template into app/features/widgets/Name, rename Sample placeholders, set constants/name.ts to the widget identifier, and register the reducer if store state is used. This ensures consistent container, UI, lib, and store file roles across the feature.

React widget conventions require standardized query and mutation naming, typed mappers, schemas, and constants management. Reducer registration must be applied when the widget uses Redux store state to maintain code quality and testability across the application.

Updating an existing widget involves refactoring its container, UI, lib, and store files to follow template conventions. This enforces correct file roles, naming patterns, and typed mappers to keep the widget maintainable and prevent regressions.

Yes, Redux is used only when the widget requires store state. If a widget does not need Redux, you can scaffold the container, UI, lib, and constants without registering a reducer, while still maintaining standardized structure and typing conventions.

Inconsistent React widgets happen without a single template enforcing file roles and naming patterns. Applying a standardized structure with clear container, UI, lib, store, and constants directories reduces onboarding time and avoids regressions across the codebase.